| Showing 1-30 of 43 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 112252 | 2023-09-04 16:20 | 2023-11-07 11:29 | MySQL Server: InnoDB storage engine | Analyzing (617 days) | S3 | 8.0.33, 8.0.34 | Any | Any | InnoDB page compression impacts checkpointing |
| 116943 | 2024-12-11 13:50 | 2024-12-20 15:18 | MySQL Server: DDL | Verified (200 days) | S3 | 8.0.40 | Any | Any | Inconsistent metadata-only table and column collation changes behavior of ALTER TABLE |
| 116944 | 2024-12-11 14:09 | 2024-12-11 14:24 | MySQL Server: Documentation | Verified (209 days) | S3 | 8.0, 8.4 | Any | Any | Documentation about online DDL missing collation changes |
| 115954 | 2024-08-28 15:17 | 2024-08-29 9:09 | MySQL Server: Logging | Verified (313 days) | S3 | 8.4.2, 8.0.x | Any | Any | Confusing warning "Cannot add field x in table y because after adding it ..." |
| 115563 | 2024-07-11 7:54 | 2024-07-16 6:53 | MySQL Server: Group Replication | Verified (357 days) | S3 | 8.0.38 | Any | Any | Group replication conflict resolutions seem inconsistent |
| 115327 | 2024-06-13 22:01 | 2024-06-19 12:26 | MySQL Server: Optimizer | Verified (384 days) | S5 | 8.0.37, 8.4.0 | Any | Any | Higher memory requirements for range optimizer in v. 8.0 vs 5.7 |
| 115062 | 2024-05-20 11:02 | 2024-05-20 15:05 | MySQL Server: Documentation | Verified (414 days) | S3 | 8.0 | Any | Any | Guidelines for estimating range optimization memory usage inaccurate |
| 114717 | 2024-04-20 18:57 | 2024-04-22 9:30 | MySQL Server: DDL | Verified (442 days) | S3 | 8.0.36 | Any | Any | Inconsistent behavior of explicit CHARSET/COLLATE column definition |
| 114468 | 2024-03-24 21:51 | 2025-05-27 12:59 | MySQL Server: InnoDB storage engine | Verified (470 days) | S5 | 8.3.0, 8.0.36 | Any | Any | Inconsistent table performance: fresh data import vs after optimization |
| 113644 | 2024-01-15 14:13 | 2024-01-16 10:53 | MySQL Server: InnoDB storage engine | Verified (540 days) | S3 | 8.0 | Any | Any | Confusing thread id vs processlist id information in SEIS |
| 113440 | 2023-12-15 13:06 | 2024-01-03 6:17 | MySQL Server: InnoDB storage engine | Verified (569 days) | S2 | 8.0.35 | Any | Any | Table spaces with instant_col information can no longer be imported |
| 112717 | 2023-10-13 15:14 | 2023-10-25 8:12 | MySQL Server: Replication | Verified (622 days) | S3 | 8.0.34 | Any | Any | Undo log truncation does not finalize when super_read_only=1 |
| 112780 | 2023-10-20 10:05 | 2023-10-23 8:57 | MySQL Server: Documentation | Verified (624 days) | S3 | 8.0.34, 8.1.0 | Any | Any | innodb_temp_data_file_path changed from relative to absolute path in 8.0 |
| 112705 | 2023-10-12 12:39 | 2023-10-12 12:53 | MySQL Server: SYS Schema | Verified (635 days) | S3 | 8.0.34 | Any | Any | sys.schema_table_statistics reset values upon index addition or removal |
| 112670 | 2023-10-09 15:47 | 2023-10-10 5:04 | MySQL Server: Documentation | Verified (637 days) | S3 | 8.0.34 | Any | Any | Documentation outdated related ANALYZE TABLE locking |
| 110111 | 2023-02-17 12:53 | 2023-02-20 12:35 | MySQL Server: Optimizer | Verified (869 days) | S5 | 8.0.31 | Any | Any | Optimizer chooses worst plan when index condition pushdown opportunity |
| 110117 | 2023-02-17 13:22 | 2023-02-17 15:32 | MySQL Server: Documentation | Verified (872 days) | S3 | 8.0 | Any | Any | Lack of instrumentation for index condition impact on the query plan |
| 109107 | 2022-11-16 8:19 | 2022-11-22 14:06 | MySQL Server: DML | Verified (965 days) | S5 | 8.0.31 | Any | Any | Non optimal query plan chosen for DELETE |
| 108824 | 2022-10-19 10:21 | 2022-10-19 10:52 | MySQL Server: Group Replication | Verified (993 days) | S3 | 8.0.31 | Any | Any | GCS_DEBUG_TRACE log not possible to rotate/archive without downtime |
| 108532 | 2022-09-19 9:32 | 2022-09-19 9:42 | MySQL Server: Documentation | Verified (1023 days) | S3 | 8.0.30 | Any | Any | Documentation missing redo log upgrade |
| 107293 | 2022-05-15 13:34 | 2022-05-21 20:52 | MySQL Server: Replication | Verified (1144 days) | S2 | 5.7.37, 8.0.28 | Any | Any | CURRENT_TIMESTAMP not safe after all? |
| 106012 | 2021-12-30 18:26 | 2022-04-06 11:48 | MySQL Server: InnoDB storage engine | Verified (1190 days) | S3 | 8.0, 5.7 | Any | Any | Table stats in P_S not updated on rows updated via FK constraint |
| 103157 | 2021-03-30 22:01 | 2021-03-31 6:32 | MySQL Server: Replication | Verified (1560 days) | S3 | 8.0.23 | Any | Any | Inconsistent terminology change in error messages |
| 102417 | 2021-01-29 9:54 | 2021-01-29 10:22 | MySQL Server: DDL | Verified (1621 days) | S3 | 5.7.33, 8.0.23 | Any | Any | Table space path for partitioned table goes crazy after CREATE TABLE ... LIKE |
| 102395 | 2021-01-27 11:33 | 2021-01-27 12:18 | MySQL Server: DDL | Verified (1623 days) | S2 | 5.7.32, 8.0.23 | Any | Any | CREATE TABLE ... LIKE inconsistent behavior in regards to DATA DIRECTORY |
| 98324 | 2020-01-22 9:57 | 2022-03-07 6:04 | MySQL Server: InnoDB storage engine | Verified (1924 days) | S2 | 5.7.26, 5.7.29, 8.0.20 | Any | Any | Deadlocks more frequent since version 5.7.26 |
| 97913 | 2019-12-06 11:15 | 2019-12-23 5:55 | MySQL Server: InnoDB storage engine | Verified (2038 days) | S3 | 5.7.28 | Any | Any | Undo logs growing during partitioning ALTER queries |
| 96853 | 2019-09-12 15:10 | 2019-09-19 10:19 | MySQL Server: Replication | Verified (2119 days) | S3 | 5.7.27 | Any | Any | Inconsistent super_read_only status when changing the variable is blocked |
| 96644 | 2019-08-25 11:58 | 2019-09-13 10:03 | MySQL Server: Replication | Verified (2125 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 |
| 96400 | 2019-08-01 13:30 | 2022-06-15 21:07 | MySQL Server: Replication | Verified (2167 days) | S3 | 5.7.25, 5.7.27 | Any | Any | MTS STOP SLAVE takes over a minute when master crashed during event logging |
| Showing 1-30 of 43 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
