Showing all 21 (Edit, Save, CSV, Feed)
ID# Date Updated Type Status Sev Version OS CPU Summary
999942020-06-26
7:57
2020-06-26
13:08
MySQL Server: OptimizerVerified
(1449 days)
S58.0AnyAnyIndex range scan is chosen where table scan takes 40% less time
1041862021-07-01
15:04
2022-01-25
17:07
MySQL Server: OptimizerClosed
(997 days)
S58.0AnyAnyToo few chunk files are created for hybrid hash join
1038692021-05-31
14:29
2021-06-03
10:21
MySQL Server: OptimizerVerified
(1108 days)
S58.0.24, 8.0.25AnyAnyDuplicate computation of aggregate function when referred in HAVING clause
1028752021-03-09
8:30
2021-03-09
9:34
MySQL Server: OptimizerVerified
(1193 days)
S38.0.23AnyAnyTree EXPLAIN shows different row estimate for filtering when sorting is used
1005972020-08-21
7:10
2024-04-18
10:19
MySQL Server: OptimizerClosed
(59 days)
S38.0AnyAnyINDEX hint does not affect count(*) execution
1000002020-06-26
7:58
2024-05-15
9:25
MySQL Server: OptimizerVerified
(1449 days)
S48.0, 8.4AnyAnyProvide an index hint that only affects the choice of index for NL join
999992020-06-26
7:58
2020-06-29
13:11
MySQL Server: OptimizerClosed
(1446 days)
S38.0.20AnyAnyEXPLAIN FORMAT=TREE does not show cost/rows for semijoin materialization
999982020-06-26
7:58
2020-06-29
12:40
MySQL Server: InnoDB storage engineDuplicate
(1446 days)
S38.0.20AnyAnyFor large ranges, the range estimate will never exceed 50%
999972020-06-26
7:58
2020-06-26
12:23
MySQL Server: InnoDB storage engineDuplicate
(1449 days)
S38.0.20AnyAnyRange estimates are usually off by a factor of 2 for large ranges
999962020-06-26
7:58
2020-06-26
8:44
MySQL Server: OptimizerVerified
(1449 days)
S48.0.20AnyAnyPrefer histogram over index statistics when eq_range_index_dive_limit is exceede
999952020-06-26
7:57
2020-06-26
13:13
MySQL Server: OptimizerVerified
(1449 days)
S38.0AnyAnyHistogram is not used for filtering estimate when index is disabled
960712019-07-02
10:43
2022-07-19
13:12
MySQL Server: InnoDB storage engineVerified
(1465 days)
S38.0.16AnyAnyTempTable engine uses much more memory than MEMORY engine for temporary table
999932020-06-26
7:57
2021-07-23
13:24
MySQL Server: OptimizerClosed
(1101 days)
S48.0.20AnyAnyAdd optimizer trace for in-memory estimate
999342020-06-19
2:32
2020-09-21
14:39
MySQL Server: OptimizerVerified
(1456 days)
S58.0.20AnyAnyHash join adds columns to the hash table that is not needed.
999332020-06-19
1:30
2020-11-11
8:38
MySQL Server: OptimizerClosed
(1311 days)
S38.0AnyAnyIn-memory hash join will only use two-thirds of join buffer
992952020-04-18
7:56
2020-04-20
10:04
MySQL Server: InnoDB storage engineVerified
(1516 days)
S28.0.19AnyAnyInnoDB in-memory estimate is wrong after an index is created
992932020-04-17
21:01
2020-04-24
23:22
MySQL Server: InnoDB storage engineDuplicate
(1512 days)
S38.0.19CentOSAnyCREATE INDEX gives in not very helpful error message when out of disk space
991662020-04-03
0:19
2020-04-04
11:58
MySQL Server: DocumentationClosed
(1532 days)
S38.0AnyAnyMySQL manual does include LATERAL tables in syntax description for join
987822020-02-28
18:57
2020-07-20
8:31
MySQL Server: InnoDB storage engineCan't repeat
(1425 days)
S58.0.19AnyAnyUsing TempTable engine for GROUP BY is slower than using MEMORY engine
987702020-02-28
4:02
2020-03-03
15:05
MySQL Server: OptimizerVerified
(1564 days)
S58.0.19AnyAnyNon-covering full index scan is always preferred over table scan for GROUP BY
986752020-02-19
20:57
2020-02-24
15:27
MySQL Server: OptimizerVerified
(1572 days)
S48.0.19AnyAnyLIMIT clause in derived table garbles EXPLAIN Note
Showing all 21 (Edit, Save, CSV, Feed)