Showing 1-30 of 39 (Edit, Save, CSV, Feed) Show Next 30 Entries »
ID# Date Updated Type Status Sev Version OS CPU Summary
445492009-04-29
17:47
2018-09-09
20:45
MySQL Server: OptimizerVerifiedS35.0.80, 5.1.34AnyAnyoptimizer incorrectly chooses table scan and filesort over index
480492009-10-14
16:46
2018-09-09
20:45
MySQL Server: OptimizerVerifiedS35.1.37, 5.5.7AnyAnySELECT MIN(1) reports differently for MERGE tables in 5.0 and 5.1
1171642025-01-09
6:17
2025-01-09
7:08
MySQL Server: OptimizerVerified
(155 days)
S38.0.36, 8.0.40AnyAnyRange estimation (index dives) overestimates the rows count on large ranges. It almost doubles the actual number of rows
1169372024-12-11
8:25
2024-12-11
15:33
MySQL Server: OptimizerVerified
(184 days)
S38.0, 8.0.40AnyAnyestimation of REF is modified by index diving of INDEX MERGE
1167102024-11-19
12:47
2024-11-20
11:02
MySQL Server: OptimizerVerified
(205 days)
S38.0AnyAnyexplain shows wrong cost value
1163352024-10-10
16:53
2024-10-11
8:04
MySQL Server: OptimizerVerified
(245 days)
S58.0.39AnyAnyMulti-valued index isn't used with some range scans on composite indexes
1158152024-08-12
2:56
2024-08-12
8:03
MySQL Server: OptimizerVerified
(305 days)
S28.4.2AnyAnyContribute by tencent: EXPLAIN FORMAT=TREE Incorrectly Shows Cost of Statement
1129022023-10-31
14:39
2024-06-10
11:08
MySQL Server: OptimizerVerified
(473 days)
S58.0.31, 8.0.35Linux (n.a.)x86 (x86_64)Optimizer in MySQL 8 is significantly slower on dependent subqueries than 5.7
1114312023-06-15
8:47
2023-06-26
14:48
MySQL Server: OptimizerVerified
(729 days)
S38.0.33Ubuntu (22.04)Other (x86_64)condition_fanout_filter optimizer wrong result?
1108482023-04-27
15:04
2023-05-03
9:59
MySQL Server: OptimizerVerified
(772 days)
S58.0.28, 8.0.33AnyAnymissing considering on order by and limit clause in cost calculation
1101112023-02-17
12:53
2023-02-20
12:35
MySQL Server: OptimizerVerified
(844 days)
S58.0.31AnyAnyOptimizer chooses worst plan when index condition pushdown opportunity
1101172023-02-17
13:22
2023-02-17
15:32
MySQL Server: DocumentationVerified
(847 days)
S38.0AnyAnyLack of instrumentation for index condition impact on the query plan
1081272022-08-12
5:57
2022-08-16
13:34
MySQL Server: OptimizerVerified
(1032 days)
S58.0.29AnyAnyMySQL optimizer chooses to a inefficient index .
1064732022-02-16
8:55
2022-03-10
9:27
MySQL Server: OptimizerVerified
(1191 days)
S38.0.28AnyAnyInner table of OUT-JOIN is nullable, after applying OUTER2INNER transformation
1049782021-09-17
19:57
2021-09-20
9:02
MySQL Server: OptimizerVerified
(1362 days)
S58.0.26, 5.7.35WindowsAnyAdding Join Index forces query optimizer to use inefficient execution plan
1008852020-09-18
3:43
2020-11-09
11:38
MySQL Server: JSONVerified
(1729 days)
S55.7.31AnyAnygenerated column index against json column is not used with different encoding
996842020-05-25
12:19
2022-06-08
12:02
MySQL Server: OptimizerVerified
(1842 days)
S35.6, 5.7, 8.0AnyAnyincorrect determination of big test
933602018-11-27
9:41
2018-12-12
14:48
MySQL Server: OptimizerVerified
(2375 days)
S55.6.16,5.7.23Linuxx86mysterious optimizer behavior
833232016-10-10
18:02
2018-04-13
12:41
MySQL Server: OptimizerVerified
(2972 days)
S35.7, 5.6, 8.0.1AnyAnyOptimizer chooses wrong plan when joining 2 tables
860362017-04-21
10:08
2018-11-13
7:55
MySQL Server: InnoDB storage engineVerified
(2973 days)
S35.7/8.0AnyAnyInnoDB FULLTEXT index has too strict innodb_ft_result_cache_limit max limit
832482016-10-03
15:57
2023-02-22
1:40
MySQL Server: OptimizerVerified
(3175 days)
S38.0.0, 5.7.15AnyAnyPartition pruning is not working with LEFT JOIN
830712016-09-21
8:02
2016-09-21
8:34
MySQL Server: OptimizerVerified
(3187 days)
S35.7.14, 5.6.*, 5.7.15AnyAnyMySQL prefers first declared index over more useful other indexes
830622016-09-20
13:18
2018-04-24
20:15
MySQL Server: OptimizerVerified
(3187 days)
S35.6.32, 5.7.14, 5.6.33, 5.7.15AnyAnyit's no longer possible to determine used key parts by looking at key_length
800672016-01-20
10:50
2020-06-17
23:13
MySQL Server: OptimizerVerified
(3432 days)
S35.6.28, 5.7.10AnyAnyIndex on BIT column is NOT used when column name only is used in WHERE clause
303422007-08-09
18:52
2015-10-07
14:54
MySQL Server: OptimizerVerified
(3537 days)
S55.0.37, 5.6.17AnyAnyEquality propagation can make optimization much slower
740832014-09-25
18:11
2014-10-09
12:58
MySQL Server: OptimizerVerified
(3900 days)
S55.6.20, 5.6.22Linux (CentOS 6.5)AnyENUM index scan is slower than INT index scan
740492014-09-24
8:01
2014-09-24
10:01
MySQL Server: OptimizerVerified
(3915 days)
S35.6.19-67.0, 5.6.22AnyAnyUpdate query use filesort instead of index
711992013-12-21
18:16
2014-01-28
17:45
MySQL Server: OptimizerVerified
(4190 days)
S35.6.14, 5.6.15, 5.5.35AnyAnyOptimizer's estimated number of rows is 2 times wrong for (loose?) index scans
711912013-12-20
15:30
2013-12-20
20:20
MySQL Server: OptimizerVerified
(4193 days)
S35.5.33AnyAnyLoose index scan is used even though full table scan/tight index scan is faster
711892013-12-20
14:56
2021-08-08
20:45
MySQL Server: DocumentationVerified
(4193 days)
S35.5, anyAnyAnyManual does not provide enough details on how loose index scan really works
  Showing 1-30 of 39 (Edit, Save, CSV, Feed) Show Next 30 Entries »