| Showing all 6 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 25459 | 2007-01-08 2:39 | 2007-02-28 13:34 | MySQL Server: Optimizer | No Feedback (6259 days) | S3 | 5.0 | Any (any) | Any | InnoDB prefers table scan over using primary key |
| 31648 | 2007-10-16 19:01 | 2012-08-30 11:22 | MySQL Server: Optimizer | Can't repeat (4249 days) | S2 | 5.1.22, 5.0.50 | Any | Any | full table scans being done when range should be used |
| 40634 | 2008-11-11 11:30 | 2011-02-16 23:43 | MySQL Server: MyISAM storage engine | Closed (5505 days) | S5 | 5.1.29, 6.0.x | Any | Any | table scan temporary table is 4x slower due to mmap instead instead of caching |
| 44549 | 2009-04-29 17:47 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.0.80, 5.1.34 | Any | Any | optimizer incorrectly chooses table scan and filesort over index |
| 47009 | 2009-08-31 9:30 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (5204 days) | S3 | azalea | Any | Any | The basic algorithm for table scan in plgin API is not actual. |
| 108159 | 2022-08-17 2:52 | 2022-08-18 11:44 | MySQL Server | Not a Bug (609 days) | S5 | MySQL 8.0 | Any | Any | A query with user-defined variables always use the table scan. |
| Showing all 6 (Edit, Save, CSV, Feed) |
