| Showing 1-30 of 44 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 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 |
| 48049 | 2009-10-14 16:46 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.1.37, 5.5.7 | Any | Any | SELECT MIN(1) reports differently for MERGE tables in 5.0 and 5.1 |
| 120142 | 2026-03-25 3:09 | 2026-03-25 20:29 | MySQL Server: JSON | Verified (52 days) | S3 | 8.0.45 | Any | Any | Incorrect result with DISTINCTROW and JSON_OBJECTAGG when replacing COALESCE(SUM(NULL),0) with constant |
| 120036 | 2026-03-12 2:09 | 2026-03-13 13:15 | MySQL Server: Optimizer | Verified (64 days) | S3 | 8.0.45 | Any | Any | Different results for semantically equivalent expressions using CASE and MIN(CASE ...) with GROUP BY on a FLOAT column |
| 120031 | 2026-03-11 14:48 | 2026-03-11 20:46 | MySQL Server: Optimizer | Verified (66 days) | S3 | 8.4.8 | Any | Any | Inconsistent INTERSECT Results in Derived Tables: Impact of PRIMARY KEY on JSON_OBJECTAGG and LEAST Operators |
| 119447 | 2025-11-23 8:34 | 2025-11-27 5:04 | MySQL Server: Optimizer | Verified (170 days) | S5 | 8.0.41 | CentOS | x86 | Prepare Statement execute much slower than normal select query |
| 119442 | 2025-11-21 20:13 | 2025-11-27 4:53 | MySQL Server: Optimizer | Verified (170 days) | S5 | 8.4.4 | Any | Any | Optimizer fails to simplify ORDER BY when column is filtered by IS NULL, causing filesort |
| 117164 | 2025-01-09 6:17 | 2025-01-09 7:08 | MySQL Server: Optimizer | Verified (492 days) | S3 | 8.0.36, 8.0.40 | Any | Any | Range estimation (index dives) overestimates the rows count on large ranges. It almost doubles the actual number of rows |
| 116937 | 2024-12-11 8:25 | 2024-12-11 15:33 | MySQL Server: Optimizer | Verified (521 days) | S3 | 8.0, 8.0.40 | Any | Any | estimation of REF is modified by index diving of INDEX MERGE |
| 116710 | 2024-11-19 12:47 | 2024-11-20 11:02 | MySQL Server: Optimizer | Verified (542 days) | S3 | 8.0 | Any | Any | explain shows wrong cost value |
| 116335 | 2024-10-10 16:53 | 2025-09-10 1:54 | MySQL Server: Optimizer | Verified (582 days) | S5 | 8.0.39 | Any | Any | Multi-valued index isn't used with some range scans on composite indexes |
| 115815 | 2024-08-12 2:56 | 2024-08-12 8:03 | MySQL Server: Optimizer | Verified (642 days) | S2 | 8.4.2 | Any | Any | Contribute by tencent: EXPLAIN FORMAT=TREE Incorrectly Shows Cost of Statement |
| 112902 | 2023-10-31 14:39 | 2024-06-10 11:08 | MySQL Server: Optimizer | Verified (810 days) | S5 | 8.0.31, 8.0.35 | Linux (n.a.) | x86 (x86_64) | Optimizer in MySQL 8 is significantly slower on dependent subqueries than 5.7 |
| 111431 | 2023-06-15 8:47 | 2023-06-26 14:48 | MySQL Server: Optimizer | Verified (1066 days) | S3 | 8.0.33 | Ubuntu (22.04) | Other (x86_64) | condition_fanout_filter optimizer wrong result? |
| 110848 | 2023-04-27 15:04 | 2023-05-03 9:59 | MySQL Server: Optimizer | Verified (1109 days) | S5 | 8.0.28, 8.0.33 | Any | Any | missing considering on order by and limit clause in cost calculation |
| 110111 | 2023-02-17 12:53 | 2023-02-20 12:35 | MySQL Server: Optimizer | Verified (1181 days) | S5 | 8.0.31 | Any | Any | Optimizer chooses worst plan when index condition pushdown opportunity |
| 110117 | 2023-02-17 13:22 | 2023-02-17 15:32 | MySQL Server: Documentation | Verified (1184 days) | S3 | 8.0 | Any | Any | Lack of instrumentation for index condition impact on the query plan |
| 108127 | 2022-08-12 5:57 | 2025-06-19 6:23 | MySQL Server: Optimizer | Verified (1369 days) | S5 | 8.0.29 | Any | Any | MySQL optimizer chooses to a inefficient index . |
| 106473 | 2022-02-16 8:55 | 2022-03-10 9:27 | MySQL Server: Optimizer | Verified (1528 days) | S3 | 8.0.28 | Any | Any | Inner table of OUT-JOIN is nullable, after applying OUTER2INNER transformation |
| 104978 | 2021-09-17 19:57 | 2021-09-20 9:02 | MySQL Server: Optimizer | Verified (1699 days) | S5 | 8.0.26, 5.7.35 | Windows | Any | Adding Join Index forces query optimizer to use inefficient execution plan |
| 100885 | 2020-09-18 3:43 | 2020-11-09 11:38 | MySQL Server: JSON | Verified (2066 days) | S5 | 5.7.31 | Any | Any | generated column index against json column is not used with different encoding |
| 99684 | 2020-05-25 12:19 | 2022-06-08 12:02 | MySQL Server: Optimizer | Verified (2179 days) | S3 | 5.6, 5.7, 8.0 | Any | Any | incorrect determination of big test |
| 93360 | 2018-11-27 9:41 | 2018-12-12 14:48 | MySQL Server: Optimizer | Verified (2712 days) | S5 | 5.6.16,5.7.23 | Linux | x86 | mysterious optimizer behavior |
| 83323 | 2016-10-10 18:02 | 2018-04-13 12:41 | MySQL Server: Optimizer | Verified (3309 days) | S3 | 5.7, 5.6, 8.0.1 | Any | Any | Optimizer chooses wrong plan when joining 2 tables |
| 86036 | 2017-04-21 10:08 | 2018-11-13 7:55 | MySQL Server: InnoDB storage engine | Verified (3310 days) | S3 | 5.7/8.0 | Any | Any | InnoDB FULLTEXT index has too strict innodb_ft_result_cache_limit max limit |
| 83248 | 2016-10-03 15:57 | 2023-02-22 1:40 | MySQL Server: Optimizer | Verified (3512 days) | S3 | 8.0.0, 5.7.15 | Any | Any | Partition pruning is not working with LEFT JOIN |
| 83071 | 2016-09-21 8:02 | 2016-09-21 8:34 | MySQL Server: Optimizer | Verified (3524 days) | S3 | 5.7.14, 5.6.*, 5.7.15 | Any | Any | MySQL prefers first declared index over more useful other indexes |
| 83062 | 2016-09-20 13:18 | 2018-04-24 20:15 | MySQL Server: Optimizer | Verified (3524 days) | S3 | 5.6.32, 5.7.14, 5.6.33, 5.7.15 | Any | Any | it's no longer possible to determine used key parts by looking at key_length |
| 80067 | 2016-01-20 10:50 | 2020-06-17 23:13 | MySQL Server: Optimizer | Verified (3769 days) | S3 | 5.6.28, 5.7.10 | Any | Any | Index on BIT column is NOT used when column name only is used in WHERE clause |
| 30342 | 2007-08-09 18:52 | 2015-10-07 14:54 | MySQL Server: Optimizer | Verified (3874 days) | S5 | 5.0.37, 5.6.17 | Any | Any | Equality propagation can make optimization much slower |
| Showing 1-30 of 44 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
