Showing 1-30 of 34 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
30342 | 2007-08-09 18:52 | 2015-10-07 14:54 | MySQL Server: Optimizer | Verified (3121 days) | S5 | 5.0.37, 5.6.17 | Any | Any | Equality propagation can make optimization much slower |
112902 | 2023-10-31 14:39 | 2024-02-26 11:07 | MySQL Server: Optimizer | Verified (57 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 |
110848 | 2023-04-27 15:04 | 2023-05-03 9:59 | MySQL Server: Optimizer | Verified (356 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 (428 days) | S5 | 8.0.31 | Any | Any | Optimizer chooses worst plan when index condition pushdown opportunity |
108127 | 2022-08-12 5:57 | 2022-08-16 13:34 | MySQL Server: Optimizer | Verified (616 days) | S5 | 8.0.29 | Any | Any | MySQL optimizer chooses to a inefficient index . |
104978 | 2021-09-17 19:57 | 2021-09-20 9:02 | MySQL Server: Optimizer | Verified (946 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 (1313 days) | S5 | 5.7.31 | Any | Any | generated column index against json column is not used with different encoding |
93360 | 2018-11-27 9:41 | 2018-12-12 14:48 | MySQL Server: Optimizer | Verified (1959 days) | S5 | 5.6.16,5.7.23 | Linux | x86 | mysterious optimizer behavior |
74083 | 2014-09-25 18:11 | 2014-10-09 12:58 | MySQL Server: Optimizer | Verified (3484 days) | S5 | 5.6.20, 5.6.22 | Linux (CentOS 6.5) | Any | ENUM index scan is slower than INT index scan |
68554 | 2013-03-03 16:16 | 2022-03-14 16:43 | MySQL Server: Optimizer | Verified (4054 days) | S5 | 5.6.10 | Any | Any | Optimizer wrongly choses covering index over ICP |
42948 | 2009-02-17 23:02 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5530 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" |
58101 | 2010-11-10 0:21 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4912 days) | S5 | 5.1.38-community-log, 5.1.54-bzr | Linux | Any | Optimizer picks wrong order of queries |
46376 | 2009-07-24 17:05 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5382 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 |
86036 | 2017-04-21 10:08 | 2018-11-13 7:55 | MySQL Server: InnoDB storage engine | Verified (2557 days) | S3 | 5.7/8.0 | Any | Any | InnoDB FULLTEXT index has too strict innodb_ft_result_cache_limit max limit |
29443 | 2007-06-29 13:28 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4940 days) | S3 | 5.1.19 | Any | Any | cost calculations are off |
111431 | 2023-06-15 8:47 | 2023-06-26 14:48 | MySQL Server: Optimizer | Verified (313 days) | S3 | 8.0.33 | Ubuntu (22.04) | Other (x86_64) | condition_fanout_filter optimizer wrong result? |
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 |
110117 | 2023-02-17 13:22 | 2023-02-17 15:32 | MySQL Server: Documentation | Verified (431 days) | S3 | 8.0 | Any | Any | Lack of instrumentation for index condition impact on the query plan |
44201 | 2009-04-10 3:04 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5061 days) | S3 | 5.1.32, 5.1.35-bzr, 6.0.11-bzr, 5.0, 5.6.99 | Any | Any | Performance problem with View |
99684 | 2020-05-25 12:19 | 2022-06-08 12:02 | MySQL Server: Optimizer | Verified (1426 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 (775 days) | S3 | 8.0.28 | Any | Any | Inner table of OUT-JOIN is nullable, after applying OUTER2INNER transformation |
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 (5329 days) | S3 | 5.1.35 | Any | Any | Not exists optimization method is not used for NULL columns in the right table |
83323 | 2016-10-10 18:02 | 2018-04-13 12:41 | MySQL Server: Optimizer | Verified (2556 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 (2759 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 (2771 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 (2771 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 |
26232 | 2007-02-09 17:28 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (6277 days) | S3 | 4.1.22, 5.0.34, 5.0.36-BK | Linux (Linux) | Any | review of bug #20944 / proof of concept attached |
80067 | 2016-01-20 10:50 | 2020-06-17 23:13 | MySQL Server: Optimizer | Verified (3016 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 |
74049 | 2014-09-24 8:01 | 2014-09-24 10:01 | MySQL Server: Optimizer | Verified (3499 days) | S3 | 5.6.19-67.0, 5.6.22 | Any | Any | Update query use filesort instead of index |
Showing 1-30 of 34 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |