Showing 1-30 of 39 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
115815 | 2024-08-12 2:56 | 2024-08-12 8:03 | MySQL Server: Optimizer | Verified (285 days) | S2 | 8.4.2 | Any | Any | Contribute by tencent: EXPLAIN FORMAT=TREE Incorrectly Shows Cost of Statement |
67351 | 2012-10-24 8:02 | 2017-05-03 16:04 | MySQL Server: Partitions | Verified (4557 days) | S2 | 5.5.27-29.0 | Linux | Any | Cardinality samples of partitioned tables sometimes widely off |
83071 | 2016-09-21 8:02 | 2016-09-21 8:34 | MySQL Server: Optimizer | Verified (3167 days) | S3 | 5.7.14, 5.6.*, 5.7.15 | Any | Any | MySQL prefers first declared index over more useful other indexes |
117164 | 2025-01-09 6:17 | 2025-01-09 7:08 | MySQL Server: Optimizer | Verified (135 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 (164 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 (185 days) | S3 | 8.0 | Any | Any | explain shows wrong cost value |
111431 | 2023-06-15 8:47 | 2023-06-26 14:48 | MySQL Server: Optimizer | Verified (709 days) | S3 | 8.0.33 | Ubuntu (22.04) | Other (x86_64) | condition_fanout_filter optimizer wrong result? |
110117 | 2023-02-17 13:22 | 2023-02-17 15:32 | MySQL Server: Documentation | Verified (827 days) | S3 | 8.0 | Any | Any | Lack of instrumentation for index condition impact on the query plan |
99684 | 2020-05-25 12:19 | 2022-06-08 12:02 | MySQL Server: Optimizer | Verified (1822 days) | S3 | 5.6, 5.7, 8.0 | Any | Any | incorrect determination of big test |
106473 | 2022-02-16 8:55 | 2022-03-10 9:27 | MySQL Server: Optimizer | Verified (1171 days) | S3 | 8.0.28 | Any | Any | Inner table of OUT-JOIN is nullable, after applying OUTER2INNER transformation |
86036 | 2017-04-21 10:08 | 2018-11-13 7:55 | MySQL Server: InnoDB storage engine | Verified (2953 days) | S3 | 5.7/8.0 | Any | Any | InnoDB FULLTEXT index has too strict innodb_ft_result_cache_limit max limit |
83323 | 2016-10-10 18:02 | 2018-04-13 12:41 | MySQL Server: Optimizer | Verified (2952 days) | S3 | 5.7, 5.6, 8.0.1 | Any | Any | Optimizer chooses wrong plan when joining 2 tables |
83248 | 2016-10-03 15:57 | 2023-02-22 1:40 | MySQL Server: Optimizer | Verified (3155 days) | S3 | 8.0.0, 5.7.15 | Any | Any | Partition pruning is not working with LEFT JOIN |
26232 | 2007-02-09 17:28 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (6673 days) | S3 | 4.1.22, 5.0.34, 5.0.36-BK | Linux (Linux) | Any | review of bug #20944 / proof of concept attached |
83062 | 2016-09-20 13:18 | 2018-04-24 20:15 | MySQL Server: Optimizer | Verified (3167 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 (3412 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 |
47454 | 2009-09-19 19:33 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5725 days) | S3 | 5.1.35 | Any | Any | Not exists optimization method is not used for NULL columns in the right table |
29443 | 2007-06-29 13:28 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5336 days) | S3 | 5.1.19 | Any | Any | cost calculations are off |
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 (5457 days) | S3 | 5.1.32, 5.1.35-bzr, 6.0.11-bzr, 5.0, 5.6.99 | Any | Any | Performance problem with View |
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 |
74049 | 2014-09-24 8:01 | 2014-09-24 10:01 | MySQL Server: Optimizer | Verified (3895 days) | S3 | 5.6.19-67.0, 5.6.22 | Any | Any | Update query use filesort instead of index |
71189 | 2013-12-20 14:56 | 2021-08-08 20:45 | MySQL Server: Documentation | Verified (4173 days) | S3 | 5.5, any | Any | Any | Manual does not provide enough details on how loose index scan really works |
71199 | 2013-12-21 18:16 | 2014-01-28 17:45 | MySQL Server: Optimizer | Verified (4170 days) | S3 | 5.6.14, 5.6.15, 5.5.35 | Any | Any | Optimizer's estimated number of rows is 2 times wrong for (loose?) index scans |
71191 | 2013-12-20 15:30 | 2013-12-20 20:20 | MySQL Server: Optimizer | Verified (4173 days) | S3 | 5.5.33 | Any | Any | Loose index scan is used even though full table scan/tight index scan is faster |
110111 | 2023-02-17 12:53 | 2023-02-20 12:35 | MySQL Server: Optimizer | Verified (824 days) | S5 | 8.0.31 | Any | Any | Optimizer chooses worst plan when index condition pushdown opportunity |
30342 | 2007-08-09 18:52 | 2015-10-07 14:54 | MySQL Server: Optimizer | Verified (3517 days) | S5 | 5.0.37, 5.6.17 | Any | Any | Equality propagation can make optimization much slower |
42948 | 2009-02-17 23:02 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5926 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" |
116335 | 2024-10-10 16:53 | 2024-10-11 8:04 | MySQL Server: Optimizer | Verified (225 days) | S5 | 8.0.39 | Any | Any | Multi-valued index isn't used with some range scans on composite indexes |
112902 | 2023-10-31 14:39 | 2024-06-10 11:08 | MySQL Server: Optimizer | Verified (453 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 |
Showing 1-30 of 39 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |