| Showing 1-10 of 72 (Edit, Save, CSV, Feed) | Show Next 10 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 104083 | 2021-06-22 8:09 | 2021-06-22 13:11 | MySQL Server: Optimizer | Verified (210 days) | S5 | 8.0.25 | Any | Any | MySQL optimizer chooses the wrong index due to 'range_uses_more_keyparts' |
| 98770 | 2020-02-28 4:02 | 2020-03-03 15:05 | MySQL Server: Optimizer | Verified (686 days) | S5 | 8.0.19 | Any | Any | Non-covering full index scan is always preferred over table scan for GROUP BY |
| 87947 | 2017-10-03 4:00 | 2018-06-11 19:57 | MySQL Server: Optimizer | Verified (1562 days) | S5 | 5.7.19 | Any | Any | Optimizer chooses ref over range when access when range access is faster |
| 38550 | 2008-08-04 21:47 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4842 days) | S5 | 5.0.60, 5.1 | Any | Any | multiple optimizer bugs for queries with references from preceding table |
| 105044 | 2021-09-26 15:32 | 2021-09-27 12:59 | MySQL Server: InnoDB storage engine | Verified (113 days) | S5 | 8.0 | Any | Any | Added page szie judgment logic like btr_cur_optimistic_insert in btr_insert_into |
| 95080 | 2019-04-23 7:24 | 2019-04-30 14:09 | MySQL Router | Verified (994 days) | S5 | 8.0.15, 8.0.16 | Oracle Linux (Oracle Linux Server 7.5, Linux 4.1.12-124.18.6.el7uek.x86_64 ) | x86 (Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz) | MySQL Router consuming mor CPU resources than it should |
| 103869 | 2021-05-31 14:29 | 2021-06-03 10:21 | MySQL Server: Optimizer | Verified (230 days) | S5 | 8.0.24, 8.0.25 | Any | Any | Duplicate computation of aggregate function when referred in HAVING clause |
| 58234 | 2010-11-16 16:26 | 2014-02-26 12:47 | MySQL Server: InnoDB storage engine | Verified (3684 days) | S5 | 5.1.49-r1, 5.5.20 | Any | Any | LENGTH() / OCTET_LENGTH() on BLOB field very slow |
| 63905 | 2012-01-02 23:47 | 2012-01-16 18:35 | MySQL Server: Optimizer | Verified (3655 days) | S5 | 5.1.60 | Microsoft Windows | Any | handler_read_next is suprisingly high and slows queries |
| 78407 | 2015-09-11 12:45 | 2015-09-15 7:50 | MySQL Server: Optimizer | Analyzing (2317 days) | S5 | 7.4.6/5.6.24 | Linux | Any | wrong index being used in subqueries? |
| Showing 1-10 of 72 (Edit, Save, CSV, Feed) | Show Next 10 Entries » |
