Showing 1-30 of 44 (Edit, Save, CSV, Feed) Show Next 30 Entries »
ID# Date Updated Type Status Sev Version OS CPU Summary
1158152024-08-12
2:56
2024-08-12
8:03
MySQL Server: OptimizerVerified
(615 days)
S28.4.2AnyAnyContribute by tencent: EXPLAIN FORMAT=TREE Incorrectly Shows Cost of Statement
673512012-10-24
8:02
2017-05-03
16:04
MySQL Server: PartitionsVerified
(4887 days)
S25.5.27-29.0LinuxAnyCardinality samples of partitioned tables sometimes widely off
830622016-09-20
13:18
2018-04-24
20:15
MySQL Server: OptimizerVerified
(3497 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
860362017-04-21
10:08
2018-11-13
7:55
MySQL Server: InnoDB storage engineVerified
(3283 days)
S35.7/8.0AnyAnyInnoDB FULLTEXT index has too strict innodb_ft_result_cache_limit max limit
830712016-09-21
8:02
2016-09-21
8:34
MySQL Server: OptimizerVerified
(3497 days)
S35.7.14, 5.6.*, 5.7.15AnyAnyMySQL prefers first declared index over more useful other indexes
832482016-10-03
15:57
2023-02-22
1:40
MySQL Server: OptimizerVerified
(3485 days)
S38.0.0, 5.7.15AnyAnyPartition pruning is not working with LEFT JOIN
833232016-10-10
18:02
2018-04-13
12:41
MySQL Server: OptimizerVerified
(3282 days)
S35.7, 5.6, 8.0.1AnyAnyOptimizer chooses wrong plan when joining 2 tables
262322007-02-09
17:28
2018-09-09
20:45
MySQL Server: OptimizerVerified
(7003 days)
S34.1.22, 5.0.34, 5.0.36-BKLinux (Linux)Anyreview of bug #20944 / proof of concept attached
1064732022-02-16
8:55
2022-03-10
9:27
MySQL Server: OptimizerVerified
(1501 days)
S38.0.28AnyAnyInner table of OUT-JOIN is nullable, after applying OUTER2INNER transformation
996842020-05-25
12:19
2022-06-08
12:02
MySQL Server: OptimizerVerified
(2152 days)
S35.6, 5.7, 8.0AnyAnyincorrect determination of big test
1101172023-02-17
13:22
2023-02-17
15:32
MySQL Server: DocumentationVerified
(1157 days)
S38.0AnyAnyLack of instrumentation for index condition impact on the query plan
1114312023-06-15
8:47
2023-06-26
14:48
MySQL Server: OptimizerVerified
(1039 days)
S38.0.33Ubuntu (22.04)Other (x86_64)condition_fanout_filter optimizer wrong result?
1167102024-11-19
12:47
2024-11-20
11:02
MySQL Server: OptimizerVerified
(515 days)
S38.0AnyAnyexplain shows wrong cost value
1169372024-12-11
8:25
2024-12-11
15:33
MySQL Server: OptimizerVerified
(494 days)
S38.0, 8.0.40AnyAnyestimation of REF is modified by index diving of INDEX MERGE
1171642025-01-09
6:17
2025-01-09
7:08
MySQL Server: OptimizerVerified
(465 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
1200312026-03-11
14:48
2026-03-11
20:46
MySQL Server: OptimizerVerified
(39 days)
S38.4.8AnyAnyInconsistent INTERSECT Results in Derived Tables: Impact of PRIMARY KEY on JSON_OBJECTAGG and LEAST Operators
1200362026-03-12
2:09
2026-03-13
13:15
MySQL Server: OptimizerVerified
(37 days)
S38.0.45AnyAnyDifferent results for semantically equivalent expressions using CASE and MIN(CASE ...) with GROUP BY on a FLOAT column
1201422026-03-25
3:09
2026-03-25
20:29
MySQL Server: JSONVerified
(25 days)
S38.0.45AnyAnyIncorrect result with DISTINCTROW and JSON_OBJECTAGG when replacing COALESCE(SUM(NULL),0) with constant
800672016-01-20
10:50
2020-06-17
23:13
MySQL Server: OptimizerVerified
(3742 days)
S35.6.28, 5.7.10AnyAnyIndex on BIT column is NOT used when column name only is used in WHERE clause
294432007-06-29
13:28
2018-09-09
20:45
MySQL Server: OptimizerVerified
(5666 days)
S35.1.19AnyAnycost calculations are off
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
442012009-04-10
3:04
2018-09-09
20:45
MySQL Server: OptimizerVerified
(5787 days)
S35.1.32, 5.1.35-bzr, 6.0.11-bzr, 5.0, 5.6.99AnyAnyPerformance problem with View
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
474542009-09-19
19:33
2018-09-09
20:45
MySQL Server: OptimizerVerified
(6055 days)
S35.1.35AnyAnyNot exists optimization method is not used for NULL columns in the right table
711912013-12-20
15:30
2013-12-20
20:20
MySQL Server: OptimizerVerified
(4503 days)
S35.5.33AnyAnyLoose index scan is used even though full table scan/tight index scan is faster
711992013-12-21
18:16
2014-01-28
17:45
MySQL Server: OptimizerVerified
(4500 days)
S35.6.14, 5.6.15, 5.5.35AnyAnyOptimizer's estimated number of rows is 2 times wrong for (loose?) index scans
740492014-09-24
8:01
2014-09-24
10:01
MySQL Server: OptimizerVerified
(4225 days)
S35.6.19-67.0, 5.6.22AnyAnyUpdate query use filesort instead of index
711892013-12-20
14:56
2021-08-08
20:45
MySQL Server: DocumentationVerified
(4503 days)
S35.5, anyAnyAnyManual does not provide enough details on how loose index scan really works
1163352024-10-10
16:53
2025-09-10
1:54
MySQL Server: OptimizerVerified
(555 days)
S58.0.39AnyAnyMulti-valued index isn't used with some range scans on composite indexes
303422007-08-09
18:52
2015-10-07
14:54
MySQL Server: OptimizerVerified
(3847 days)
S55.0.37, 5.6.17AnyAnyEquality propagation can make optimization much slower
  Showing 1-30 of 44 (Edit, Save, CSV, Feed) Show Next 30 Entries »