| Showing all 17 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 37851 | 2008-07-03 20:20 | 2011-02-16 23:43 | MySQL Server: Optimizer | Closed (4898 days) | S1 | 6.0 | Any | Any | Crash in test_if_skip_sort_order tab->select is zero |
| 43578 | 2009-03-12 9:33 | 2011-02-16 23:43 | MySQL Server: Optimizer | Can't repeat (5305 days) | S3 | 6.0.11-bzr,5.4 | Any | Any | MyISAM&Maria gives wrong rows with range access ORDER BY DESC on date index |
| 43600 | 2009-03-12 15:16 | 2011-02-16 23:43 | MySQL Server: Optimizer | Closed (4895 days) | S3 | 6.0, 5.4 | Any | Any | Wrong query result if pushed index condition returns 2 |
| 45220 | 2009-05-31 19:02 | 2020-05-03 20:45 | MySQL Server: Optimizer | Duplicate (5341 days) | S3 | 5.4 | Any | Any | Queries of the pattern - WHERE <col> <condition> HAVING X ORDER BY `pk` fail |
| 45928 | 2009-07-03 0:41 | 2011-02-16 23:44 | MySQL Server: Optimizer | Can't repeat (5306 days) | S3 | 5.4 | Any | Any | Differing query results depending on MRR and engine_condition_pushdown settings |
| 46077 | 2009-07-09 10:18 | 2011-02-16 23:44 | MySQL Server: Optimizer | Can't repeat (5269 days) | S3 | 5.4 | Any | Any | wrong result: HAVING + ORDER BY + MyISAM + ICP returns extra rows |
| 37415 | 2008-06-15 17:56 | 2011-02-16 23:43 | MySQL Server: Optimizer | Can't repeat (5258 days) | S1 | 6.0 | Any | Any | Crash in row_sel_field_store_in_mysql_format on multiple-table update (innodb) |
| 35080 | 2008-03-05 13:00 | 2018-09-09 20:45 | MySQL Server: Optimizer | Duplicate (5165 days) | S3 | 6.0-falcon-team,6.0 | Any | Any | Innodb crash at mem_block_get_len line 72 |
| 34591 | 2008-02-15 11:56 | 2016-10-09 20:45 | MySQL Server: Optimizer | Duplicate (5202 days) | S1 | 6.0.4 | Any | Any | Innob crash in row_sel_store_mysql_rec() on multi-table delete |
| 68554 | 2013-03-03 16:16 | 2022-03-14 16:43 | MySQL Server: Optimizer | Verified (4049 days) | S5 | 5.6.10 | Any | Any | Optimizer wrongly choses covering index over ICP |
| 69846 | 2013-07-26 9:15 | 2013-08-06 17:38 | MySQL Server: Documentation | Closed (3908 days) | S5 | 5.6.12 | Linux | Any | ICP does not work on UNIQUE indexes |
| 83071 | 2016-09-21 8:02 | 2016-09-21 8:34 | MySQL Server: Optimizer | Verified (2766 days) | S3 | 5.7.14, 5.6.*, 5.7.15 | Any | Any | MySQL prefers first declared index over more useful other indexes |
| 83470 | 2016-10-20 18:24 | 2017-05-16 2:53 | MySQL Server: Partitions | Closed (2529 days) | S3 | 5.7.16-debug-log | Any | Any | Reverse scan on a partitioned table does ICP check incorrectly, causing slowdown |
| 108239 | 2022-08-23 8:46 | 2022-09-05 8:03 | MySQL Server: Optimizer | Verified (591 days) | S5 | 8.0 | Any | Any | Optimizer don't choose ICP when using filesort. |
| 110117 | 2023-02-17 13:22 | 2023-02-17 15:32 | MySQL Server: Documentation | Verified (426 days) | S3 | 8.0 | Any | Any | Lack of instrumentation for index condition impact on the query plan |
| 110111 | 2023-02-17 12:53 | 2023-02-20 12:35 | MySQL Server: Optimizer | Verified (423 days) | S5 | 8.0.31 | Any | Any | Optimizer chooses worst plan when index condition pushdown opportunity |
| 112876 | 2023-10-28 16:43 | 2023-11-10 11:34 | MySQL Server: Optimizer | Not a Bug (160 days) | S3 | 8.0.33 | Any | Any | ICP (Index condition pushdown) causing BIGINT UNSIGNED value out of range error |
| Showing all 17 (Edit, Save, CSV, Feed) |
