| Showing 1-30 of 80 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 106323 | 2022-01-28 9:48 | 2022-10-18 0:48 | MySQL Server | Closed (1001 days) | S3 | 8.0, 5.7 | Any | Any | relay_log_space_limit VALID_RANGE improperly defined |
| 110117 | 2023-02-17 13:22 | 2023-02-17 15:32 | MySQL Server: Documentation | Verified (879 days) | S3 | 8.0 | Any | Any | Lack of instrumentation for index condition impact on the query plan |
| 110111 | 2023-02-17 12:53 | 2023-02-20 12:35 | MySQL Server: Optimizer | Verified (876 days) | S5 | 8.0.31 | Any | Any | Optimizer chooses worst plan when index condition pushdown opportunity |
| 109701 | 2023-01-19 11:11 | 2023-02-21 22:39 | MySQL Server: mysqldump Command-line Client | Duplicate (875 days) | S3 | 8.0.32 | Any | Any | Fix for #33630199 in 8.0.32 introduces regression when --set-gtid-purged=OFF |
| 109700 | 2023-01-19 10:52 | 2023-05-31 3:36 | MySQL Server: Documentation | Closed (776 days) | S3 | 8.0.32 | Any | Any | Fix for #33630199 in 8.0.32 not reflected in the documentation and release notes |
| 109107 | 2022-11-16 8:19 | 2022-11-22 14:06 | MySQL Server: DML | Verified (972 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 (1000 days) | S3 | 8.0.31 | Any | Any | GCS_DEBUG_TRACE log not possible to rotate/archive without downtime |
| 108821 | 2022-10-19 10:01 | 2022-11-16 13:46 | MySQL Server: Documentation | Closed (972 days) | S3 | 8.0.31 | Any | Any | DOC issue with group_replication_communication_debug_options description |
| 108532 | 2022-09-19 9:32 | 2022-09-19 9:42 | MySQL Server: Documentation | Verified (1030 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 (1151 days) | S2 | 5.7.37, 8.0.28 | Any | Any | CURRENT_TIMESTAMP not safe after all? |
| 112252 | 2023-09-04 16:20 | 2023-11-07 11:29 | MySQL Server: InnoDB storage engine | Analyzing (624 days) | S3 | 8.0.33, 8.0.34 | Any | Any | InnoDB page compression impacts checkpointing |
| 106012 | 2021-12-30 18:26 | 2022-04-06 11:48 | MySQL Server: InnoDB storage engine | Verified (1197 days) | S3 | 8.0, 5.7 | Any | Any | Table stats in P_S not updated on rows updated via FK constraint |
| 104718 | 2021-08-25 9:59 | 2021-09-28 1:00 | MySQL Server: Documentation | No Feedback (1387 days) | S3 | 8.0.25 | Any | Any | Documentation inaccurate about UPDATE_TIME in I_S.tables |
| 104099 | 2021-06-24 8:53 | 2021-08-26 23:04 | MySQL Server: Documentation | Closed (1419 days) | S3 | 5.6, 5.7 | Any | Any | Replication and max_allowed_packet documentation incomplete for 5.6 and 5.7 |
| 103157 | 2021-03-30 22:01 | 2021-03-31 6:32 | MySQL Server: Replication | Verified (1567 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 (1628 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 (1630 days) | S2 | 5.7.32, 8.0.23 | Any | Any | CREATE TABLE ... LIKE inconsistent behavior in regards to DATA DIRECTORY |
| 101142 | 2020-10-12 22:49 | 2020-10-13 12:50 | MySQL Server: Logging | Not a Bug (1736 days) | S3 | 5.7.31, 8.0.20 | Any | Any | Queries long due to Lock_time not logged in the slow log |
| 98324 | 2020-01-22 9:57 | 2022-03-07 6:04 | MySQL Server: InnoDB storage engine | Verified (1931 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 (2045 days) | S3 | 5.7.28 | Any | Any | Undo logs growing during partitioning ALTER queries |
| 114717 | 2024-04-20 18:57 | 2024-04-22 9:30 | MySQL Server: DDL | Verified (449 days) | S3 | 8.0.36 | Any | Any | Inconsistent behavior of explicit CHARSET/COLLATE column definition |
| 116944 | 2024-12-11 14:09 | 2024-12-11 14:24 | MySQL Server: Documentation | Verified (216 days) | S3 | 8.0, 8.4 | Any | Any | Documentation about online DDL missing collation changes |
| 116943 | 2024-12-11 13:50 | 2024-12-20 15:18 | MySQL Server: DDL | Verified (207 days) | S3 | 8.0.40 | Any | Any | Inconsistent metadata-only table and column collation changes behavior of ALTER TABLE |
| 115954 | 2024-08-28 15:17 | 2024-08-29 9:09 | MySQL Server: Logging | Verified (320 days) | S3 | 8.4.2, 8.0.x | Any | Any | Confusing warning "Cannot add field x in table y because after adding it ..." |
| 115798 | 2024-08-08 11:54 | 2024-09-18 9:51 | Shell Upgrade Checker | Closed (300 days) | S2 | 8.4.1 | Any | Any | util.checkForServerUpgrade() claims upgrade version 8.0.x to 8.4.x not supported |
| 115563 | 2024-07-11 7:54 | 2024-07-16 6:53 | MySQL Server: Group Replication | Verified (364 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 (391 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 (421 days) | S3 | 8.0 | Any | Any | Guidelines for estimating range optimization memory usage inaccurate |
| 114924 | 2024-05-08 14:01 | 2025-06-16 5:39 | MySQL Server: InnoDB storage engine | Won't fix (29 days) | S5 | 8.0.37 | Any | Any | Significant regression between 8.0.25 and 8.0.37 in a simple OLTP workload |
| 114815 | 2024-04-29 12:15 | 2025-01-10 11:43 | Shell Upgrade Checker | Closed (216 days) | S3 | 8.0.36 | Any | Any | Prepared statement in stored procedure - error on util.checkForServerUpgrade |
| Showing 1-30 of 80 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
