| « Show Previous 30 Entries | Showing 31-47 of 47 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 89182 | 2018-01-11 9:51 | 2018-01-11 13:10 | MySQL Server: Optimizer | Verified (3014 days) | S3 | 5.6.38, 5.7.20, 8.0.3 | Any | Any | Optimizer unable to ignore index part entering less optimal query plan |
| 92558 | 2018-09-25 12:02 | 2018-09-26 5:47 | MySQL Server: Information schema | Verified (2756 days) | S3 | 5.7.23, 8.0.12 | Any | Any | information_schema.innodb_trx trx_is_read_only not set for all RO transactions |
| 94187 | 2019-02-04 9:14 | 2019-02-05 5:44 | MySQL Server: Command-line Clients | Verified (2625 days) | S3 | 5.7.21 | Any | Any | Downgrade minor 5.7 version leaves incorrect innodb_table_stats schema |
| 96001 | 2019-06-26 12:07 | 2019-09-02 12:14 | MySQL Server: MyISAM storage engine | Verified (2483 days) | S3 | 8.0.16, 5.7.26 | Any | Any | No warning when creating foreign key in MyISAM tables |
| 96644 | 2019-08-25 11:58 | 2019-09-13 10:03 | MySQL Server: Replication | Verified (2404 days) | S3 | 5.7.26, 5.7.27 | Any | Any | Set read_only on a master waiting for semi-sync ACK blocked on global read lock |
| 96853 | 2019-09-12 15:10 | 2019-09-19 10:19 | MySQL Server: Replication | Verified (2398 days) | S3 | 5.7.27 | Any | Any | Inconsistent super_read_only status when changing the variable is blocked |
| 97913 | 2019-12-06 11:15 | 2019-12-23 5:55 | MySQL Server: InnoDB storage engine | Verified (2317 days) | S3 | 5.7.28 | Any | Any | Undo logs growing during partitioning ALTER queries |
| 102417 | 2021-01-29 9:54 | 2021-01-29 10:22 | MySQL Server: DDL | Verified (1900 days) | S3 | 5.7.33, 8.0.23 | Any | Any | Table space path for partitioned table goes crazy after CREATE TABLE ... LIKE |
| 103157 | 2021-03-30 22:01 | 2021-03-31 6:32 | MySQL Server: Replication | Verified (1839 days) | S3 | 8.0.23 | Any | Any | Inconsistent terminology change in error messages |
| 106012 | 2021-12-30 18:26 | 2026-02-19 12:39 | MySQL Server: InnoDB storage engine | Verified (53 days) | S3 | 8.0, 5.7 | Any | Any | Table stats in P_S not updated on rows updated via FK constraint |
| 108532 | 2022-09-19 9:32 | 2022-09-19 9:42 | MySQL Server: Documentation | Verified (1302 days) | S3 | 8.0.30 | Any | Any | Documentation missing redo log upgrade |
| 108824 | 2022-10-19 10:21 | 2022-10-19 10:52 | MySQL Server: Group Replication | Verified (1272 days) | S3 | 8.0.31 | Any | Any | GCS_DEBUG_TRACE log not possible to rotate/archive without downtime |
| 114468 | 2024-03-24 21:51 | 2025-05-27 12:59 | MySQL Server: InnoDB storage engine | Verified (749 days) | S5 | 8.3.0, 8.0.36 | Any | Any | Inconsistent table performance: fresh data import vs after optimization |
| 109107 | 2022-11-16 8:19 | 2022-11-22 14:06 | MySQL Server: DML | Verified (1244 days) | S5 | 8.0.31 | Any | Any | Non optimal query plan chosen for DELETE |
| 115327 | 2024-06-13 22:01 | 2024-06-19 12:26 | MySQL Server: Optimizer | Verified (663 days) | S5 | 8.0.37, 8.4.0 | Any | Any | Higher memory requirements for range optimizer in v. 8.0 vs 5.7 |
| 119066 | 2025-09-24 13:06 | 2025-10-03 11:03 | MySQL Server: Optimizer | Verified (196 days) | S5 | 8.0.40+ | Any | Any | MySQL 8.0.40+ is about 2-3x times slower than 8.0.39 in particular index scan scenario |
| 110111 | 2023-02-17 12:53 | 2023-02-20 12:35 | MySQL Server: Optimizer | Verified (1148 days) | S5 | 8.0.31 | Any | Any | Optimizer chooses worst plan when index condition pushdown opportunity |
| « Show Previous 30 Entries | Showing 31-47 of 47 (Edit, Save, CSV, Feed) |
