| Showing all 19 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 96071 | 2019-07-02 10:43 | 2020-06-10 12:30 | MySQL Server: InnoDB storage engine | Verified (329 days) | S3 | 8.0.16 | Any | Any | TempTable engine uses much more memory than MEMORY engine for temporary table |
| 98675 | 2020-02-19 20:57 | 2020-02-24 15:27 | MySQL Server: Optimizer | Verified (436 days) | S4 | 8.0.19 | Any | Any | LIMIT clause in derived table garbles EXPLAIN Note |
| 98770 | 2020-02-28 4:02 | 2020-03-03 15:05 | MySQL Server: Optimizer | Verified (428 days) | S5 | 8.0.19 | Any | Any | Non-covering full index scan is always preferred over table scan for GROUP BY |
| 98782 | 2020-02-28 18:57 | 2020-07-20 8:31 | MySQL Server: InnoDB storage engine | Can't repeat (289 days) | S5 | 8.0.19 | Any | Any | Using TempTable engine for GROUP BY is slower than using MEMORY engine |
| 99166 | 2020-04-03 0:19 | 2020-04-04 11:58 | MySQL Server: Documentation | Closed (396 days) | S3 | 8.0 | Any | Any | MySQL manual does include LATERAL tables in syntax description for join |
| 99293 | 2020-04-17 21:01 | 2020-04-24 23:22 | MySQL Server: InnoDB storage engine | Duplicate (376 days) | S3 | 8.0.19 | CentOS | Any | CREATE INDEX gives in not very helpful error message when out of disk space |
| 99295 | 2020-04-18 7:56 | 2020-04-20 10:04 | MySQL Server: InnoDB storage engine | Verified (380 days) | S2 | 8.0.19 | Any | Any | InnoDB in-memory estimate is wrong after an index is created |
| 99933 | 2020-06-19 1:30 | 2020-11-11 8:38 | MySQL Server: Optimizer | Closed (175 days) | S3 | 8.0 | Any | Any | In-memory hash join will only use two-thirds of join buffer |
| 99934 | 2020-06-19 2:32 | 2020-09-21 14:39 | MySQL Server: Optimizer | Verified (320 days) | S5 | 8.0.20 | Any | Any | Hash join adds columns to the hash table that is not needed. |
| 99993 | 2020-06-26 7:57 | 2020-06-30 4:14 | MySQL Server: Optimizer | Verified (313 days) | S4 | 8.0.20 | Any | Any | Add optimizer trace for in-memory estimate |
| 99994 | 2020-06-26 7:57 | 2020-06-26 13:08 | MySQL Server: Optimizer | Verified (313 days) | S5 | 8.0 | Any | Any | Index range scan is chosen where table scan takes 40% less time |
| 99995 | 2020-06-26 7:57 | 2020-06-26 13:13 | MySQL Server: Optimizer | Verified (313 days) | S3 | 8.0 | Any | Any | Histogram is not used for filtering estimate when index is disabled |
| 99996 | 2020-06-26 7:58 | 2020-06-26 8:44 | MySQL Server: Optimizer | Verified (313 days) | S4 | 8.0.20 | Any | Any | Prefer histogram over index statistics when eq_range_index_dive_limit is exceede |
| 99997 | 2020-06-26 7:58 | 2020-06-26 12:23 | MySQL Server: InnoDB storage engine | Duplicate (313 days) | S3 | 8.0.20 | Any | Any | Range estimates are usually off by a factor of 2 for large ranges |
| 99998 | 2020-06-26 7:58 | 2020-06-29 12:40 | MySQL Server: InnoDB storage engine | Duplicate (310 days) | S3 | 8.0.20 | Any | Any | For large ranges, the range estimate will never exceed 50% |
| 99999 | 2020-06-26 7:58 | 2020-06-29 13:11 | MySQL Server: Optimizer | Closed (310 days) | S3 | 8.0.20 | Any | Any | EXPLAIN FORMAT=TREE does not show cost/rows for semijoin materialization |
| 100000 | 2020-06-26 7:58 | 2020-07-16 2:07 | MySQL Server: Optimizer | Verified (313 days) | S4 | 8.0.20 | Any | Any | Provide an index hint that only affects the choice of index for NL join |
| 100597 | 2020-08-21 7:10 | 2020-08-24 13:07 | MySQL Server: Optimizer | Verified (254 days) | S3 | 8.0 | Any | Any | INDEX hint does not affect count(*) execution |
| 102875 | 2021-03-09 8:30 | 2021-03-09 9:34 | MySQL Server: Optimizer | Verified (57 days) | S3 | 8.0.23 | Any | Any | Tree EXPLAIN shows different row estimate for filtering when sorting is used |
| Showing all 19 (Edit, Save, CSV, Feed) |
