| Showing 1-30 of 70 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 104099 | 2021-06-24 8:53 | 2021-08-26 23:04 | MySQL Server: Documentation | Closed (964 days) | S3 | 5.6, 5.7 | Any | Any | Replication and max_allowed_packet documentation incomplete for 5.6 and 5.7 |
| 72057 | 2014-03-17 10:58 | 2014-03-20 16:16 | MySQL Server: Documentation | Closed (3680 days) | S3 | 5.1 | Any | Any | Wrong documentation sections in "Upgrading from MySQL 5.0 to 5.1" |
| 73374 | 2014-07-24 11:15 | 2015-08-21 14:47 | MySQL Server | Closed (3161 days) | S3 | 5.5 5.6 5.7 | Any | Any | CHECKSUM TABLE results differ across MySQL versions |
| 73725 | 2014-08-26 10:12 | 2014-10-21 19:06 | MySQL Server: Documentation | Closed (3465 days) | S2 | 5.6 5.7 | Any | Any | innodb_flush_log_at_trx_commit documented behavior much different since 5.6 |
| 70369 | 2013-09-17 16:07 | 2014-01-03 15:35 | MySQL Server: Documentation | Closed (3756 days) | S3 | 5.5 5.6 | Any | Any | Undocummented behavior of InnoDB tables using CHAR data type |
| 73582 | 2014-08-14 12:18 | 2014-09-29 16:48 | MySQL Server: Documentation | Closed (3487 days) | S3 | 5.6 5.7 | Any | Any | Documentation says group commit for the binary log works only if sync_binlog=0 |
| 112714 | 2023-10-13 12:45 | 2023-10-16 14:02 | MySQL Server: Clone Plugin | Can't repeat (186 days) | S3 | 8.0.34 | Any | Any | Assertion failure: clone0api.cc:1159:ib::fatal in cloning when undo_x_trunc.log |
| 69624 | 2013-06-30 13:48 | 2014-11-26 15:31 | MySQL Server: Documentation | Won't fix (3429 days) | S3 | 5.5 | Any | Any | Sometimes Memory + Events status are printed to error log on mysqld shutdown |
| 101142 | 2020-10-12 22:49 | 2020-10-13 12:50 | MySQL Server: Logging | Not a Bug (1281 days) | S3 | 5.7.31, 8.0.20 | Any | Any | Queries long due to Lock_time not logged in the slow log |
| 102395 | 2021-01-27 11:33 | 2021-01-27 12:18 | MySQL Server: DDL | Verified (1175 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 (1476 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 (1590 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 (1671 days) | S3 | 5.7.27 | Any | Any | Inconsistent super_read_only status when changing the variable is blocked |
| 114468 | 2024-03-24 21:51 | 2024-04-10 8:34 | MySQL Server: InnoDB storage engine | Verified (22 days) | S5 | 8.3.0, 8.0.36 | Any | Any | Inconsistent table performance: fresh data import vs after optimization |
| 102417 | 2021-01-29 9:54 | 2021-01-29 10:22 | MySQL Server: DDL | Verified (1173 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 (1112 days) | S3 | 8.0.23 | Any | Any | Inconsistent terminology change in error messages |
| 96644 | 2019-08-25 11:58 | 2019-09-13 10:03 | MySQL Server: Replication | Verified (1677 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 |
| 104718 | 2021-08-25 9:59 | 2021-09-28 1:00 | MySQL Server: Documentation | No Feedback (932 days) | S3 | 8.0.25 | Any | Any | Documentation inaccurate about UPDATE_TIME in I_S.tables |
| 106012 | 2021-12-30 18:26 | 2022-04-06 11:48 | MySQL Server: InnoDB storage engine | Verified (742 days) | S3 | 8.0, 5.7 | Any | Any | Table stats in P_S not updated on rows updated via FK constraint |
| 106323 | 2022-01-28 9:48 | 2022-10-18 0:48 | MySQL Server | Closed (546 days) | S3 | 8.0, 5.7 | Any | Any | relay_log_space_limit VALID_RANGE improperly defined |
| 107293 | 2022-05-15 13:34 | 2022-05-21 20:52 | MySQL Server: Replication | Verified (696 days) | S2 | 5.7.37, 8.0.28 | Any | Any | CURRENT_TIMESTAMP not safe after all? |
| 108532 | 2022-09-19 9:32 | 2022-09-19 9:42 | MySQL Server: Documentation | Verified (575 days) | S3 | 8.0.30 | Any | Any | Documentation missing redo log upgrade |
| 108821 | 2022-10-19 10:01 | 2022-11-16 13:46 | MySQL Server: Documentation | Closed (517 days) | S3 | 8.0.31 | Any | Any | DOC issue with group_replication_communication_debug_options description |
| 108824 | 2022-10-19 10:21 | 2022-10-19 10:52 | MySQL Server: Group Replication | Verified (545 days) | S3 | 8.0.31 | Any | Any | GCS_DEBUG_TRACE log not possible to rotate/archive without downtime |
| 109107 | 2022-11-16 8:19 | 2022-11-22 14:06 | MySQL Server: DML | Verified (517 days) | S5 | 8.0.31 | Any | Any | Non optimal query plan chosen for DELETE |
| 109700 | 2023-01-19 10:52 | 2023-05-31 3:36 | MySQL Server: Documentation | Closed (321 days) | S3 | 8.0.32 | Any | Any | Fix for #33630199 in 8.0.32 not reflected in the documentation and release notes |
| 109701 | 2023-01-19 11:11 | 2023-02-21 22:39 | MySQL Server: mysqldump Command-line Client | Duplicate (420 days) | S3 | 8.0.32 | Any | Any | Fix for #33630199 in 8.0.32 introduces regression when --set-gtid-purged=OFF |
| 110111 | 2023-02-17 12:53 | 2023-02-20 12:35 | MySQL Server: Optimizer | Verified (421 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 (424 days) | S3 | 8.0 | Any | Any | Lack of instrumentation for index condition impact on the query plan |
| 112252 | 2023-09-04 16:20 | 2023-11-07 11:29 | MySQL Server: InnoDB storage engine | Analyzing (169 days) | S3 | 8.0.33, 8.0.34 | Any | Any | InnoDB page compression impacts checkpointing |
| Showing 1-30 of 70 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
