| Showing 1-30 of 39 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 71189 | 2013-12-20 14:56 | 2021-08-08 20:45 | MySQL Server: Documentation | Verified (4168 days) | S3 | 5.5, any | Any | Any | Manual does not provide enough details on how loose index scan really works |
| 110117 | 2023-02-17 13:22 | 2023-02-17 15:32 | MySQL Server: Documentation | Verified (822 days) | S3 | 8.0 | Any | Any | Lack of instrumentation for index condition impact on the query plan |
| 86036 | 2017-04-21 10:08 | 2018-11-13 7:55 | MySQL Server: InnoDB storage engine | Verified (2948 days) | S3 | 5.7/8.0 | Any | Any | InnoDB FULLTEXT index has too strict innodb_ft_result_cache_limit max limit |
| 100885 | 2020-09-18 3:43 | 2020-11-09 11:38 | MySQL Server: JSON | Verified (1704 days) | S5 | 5.7.31 | Any | Any | generated column index against json column is not used with different encoding |
| 83323 | 2016-10-10 18:02 | 2018-04-13 12:41 | MySQL Server: Optimizer | Verified (2947 days) | S3 | 5.7, 5.6, 8.0.1 | Any | Any | Optimizer chooses wrong plan when joining 2 tables |
| 83071 | 2016-09-21 8:02 | 2016-09-21 8:34 | MySQL Server: Optimizer | Verified (3162 days) | S3 | 5.7.14, 5.6.*, 5.7.15 | Any | Any | MySQL prefers first declared index over more useful other indexes |
| 93360 | 2018-11-27 9:41 | 2018-12-12 14:48 | MySQL Server: Optimizer | Verified (2350 days) | S5 | 5.6.16,5.7.23 | Linux | x86 | mysterious optimizer behavior |
| 104978 | 2021-09-17 19:57 | 2021-09-20 9:02 | MySQL Server: Optimizer | Verified (1337 days) | S5 | 8.0.26, 5.7.35 | Windows | Any | Adding Join Index forces query optimizer to use inefficient execution plan |
| 106473 | 2022-02-16 8:55 | 2022-03-10 9:27 | MySQL Server: Optimizer | Verified (1166 days) | S3 | 8.0.28 | Any | Any | Inner table of OUT-JOIN is nullable, after applying OUTER2INNER transformation |
| 99684 | 2020-05-25 12:19 | 2022-06-08 12:02 | MySQL Server: Optimizer | Verified (1817 days) | S3 | 5.6, 5.7, 8.0 | Any | Any | incorrect determination of big test |
| 108127 | 2022-08-12 5:57 | 2022-08-16 13:34 | MySQL Server: Optimizer | Verified (1007 days) | S5 | 8.0.29 | Any | Any | MySQL optimizer chooses to a inefficient index . |
| 110111 | 2023-02-17 12:53 | 2023-02-20 12:35 | MySQL Server: Optimizer | Verified (819 days) | S5 | 8.0.31 | Any | Any | Optimizer chooses worst plan when index condition pushdown opportunity |
| 110848 | 2023-04-27 15:04 | 2023-05-03 9:59 | MySQL Server: Optimizer | Verified (747 days) | S5 | 8.0.28, 8.0.33 | Any | Any | missing considering on order by and limit clause in cost calculation |
| 111431 | 2023-06-15 8:47 | 2023-06-26 14:48 | MySQL Server: Optimizer | Verified (704 days) | S3 | 8.0.33 | Ubuntu (22.04) | Other (x86_64) | condition_fanout_filter optimizer wrong result? |
| 112902 | 2023-10-31 14:39 | 2024-06-10 11:08 | MySQL Server: Optimizer | Verified (448 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 |
| 115815 | 2024-08-12 2:56 | 2024-08-12 8:03 | MySQL Server: Optimizer | Verified (280 days) | S2 | 8.4.2 | Any | Any | Contribute by tencent: EXPLAIN FORMAT=TREE Incorrectly Shows Cost of Statement |
| 116335 | 2024-10-10 16:53 | 2024-10-11 8:04 | MySQL Server: Optimizer | Verified (220 days) | S5 | 8.0.39 | Any | Any | Multi-valued index isn't used with some range scans on composite indexes |
| 116710 | 2024-11-19 12:47 | 2024-11-20 11:02 | MySQL Server: Optimizer | Verified (180 days) | S3 | 8.0 | Any | Any | explain shows wrong cost value |
| 116937 | 2024-12-11 8:25 | 2024-12-11 15:33 | MySQL Server: Optimizer | Verified (159 days) | S3 | 8.0, 8.0.40 | Any | Any | estimation of REF is modified by index diving of INDEX MERGE |
| 117164 | 2025-01-09 6:17 | 2025-01-09 7:08 | MySQL Server: Optimizer | Verified (130 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 |
| 68554 | 2013-03-03 16:16 | 2022-03-14 16:43 | MySQL Server: Optimizer | Verified (4445 days) | S5 | 5.6.10 | Any | Any | Optimizer wrongly choses covering index over ICP |
| 29443 | 2007-06-29 13:28 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5331 days) | S3 | 5.1.19 | Any | Any | cost calculations are off |
| 42948 | 2009-02-17 23:02 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5921 days) | S5 | 5.0.67-0ubuntu6, 6.0.11 | Linux (Ubuntu 8.10) | Any | MySQL Optimizer does not properly use Indexes on Views with "Group By" |
| 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 |
| 44201 | 2009-04-10 3:04 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5452 days) | S3 | 5.1.32, 5.1.35-bzr, 6.0.11-bzr, 5.0, 5.6.99 | Any | Any | Performance problem with View |
| 46376 | 2009-07-24 17:05 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5773 days) | S5 | 5.0.85, 5.1.36, 5.1.38, 5.1.39 | Windows (XP) | Any | Optimizer choose wrong index even when where clause and order-by are covered |
| 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 |
| 47454 | 2009-09-19 19:33 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5720 days) | S3 | 5.1.35 | Any | Any | Not exists optimization method is not used for NULL columns in the right table |
| 58101 | 2010-11-10 0:21 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5303 days) | S5 | 5.1.38-community-log, 5.1.54-bzr | Linux | Any | Optimizer picks wrong order of queries |
| 83248 | 2016-10-03 15:57 | 2023-02-22 1:40 | MySQL Server: Optimizer | Verified (3150 days) | S3 | 8.0.0, 5.7.15 | Any | Any | Partition pruning is not working with LEFT JOIN |
| Showing 1-30 of 39 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
