Showing 1-30 of 78 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
77826 | 2015-07-24 8:19 | 2015-10-13 6:41 | MySQL Server: Replication | Verified (3194 days) | S1 | 5.6.25, 5.6.26 | Any | Any | Transaction applied partially on a slave with relay_log_info_repository=table |
69580 | 2013-06-26 9:41 | 2013-10-15 18:02 | MySQL Server: DDL | Closed (3845 days) | S2 | 5.6 | Any | Any | Renaming a column in Online DDL requires table copy for binary data types |
84564 | 2017-01-19 13:56 | 2017-12-04 7:19 | MySQL Server: Replication | Duplicate (2334 days) | S2 | 5.7, 5.7.17 | Any | Any | Inconsistent GRANT behavior on master and slave breaks replication |
84574 | 2017-01-20 0:39 | 2017-02-09 12:53 | MySQL Server: Group Replication | Not a Bug (2632 days) | S2 | 5.7.17 | Any | Any | In Group Replication, DDL execute on partitioned node leads to split brain |
82599 | 2016-08-16 14:14 | 2022-06-02 20:27 | MySQL Server: Replication | Verified (2808 days) | S2 | 5.7.14,5.6, 5.6.32 | Any | Any | slave_type_conversions messing with data which still fits within allowed range |
85251 | 2017-03-01 13:16 | 2017-10-27 8:22 | MySQL Server: Replication | Closed (2400 days) | S2 | 5.7.17, 8.0.0 | Any | Any | Memory leak in master-master GTID replication with sync_relay_log_info |
107293 | 2022-05-15 13:34 | 2022-05-21 20:52 | MySQL Server: Replication | Verified (705 days) | S2 | 5.7.37, 8.0.28 | Any | Any | CURRENT_TIMESTAMP not safe after all? |
85371 | 2017-03-08 10:46 | 2018-01-18 10:36 | MySQL Server: Replication | Closed (2344 days) | S2 | 5.7.17 | Any | Any | Memory leak in multi-source replication when binlog_rows_query_log_events=1 |
102395 | 2021-01-27 11:33 | 2021-01-27 12:18 | MySQL Server: DDL | Verified (1184 days) | S2 | 5.7.32, 8.0.23 | Any | Any | CREATE TABLE ... LIKE inconsistent behavior in regards to DATA DIRECTORY |
92690 | 2018-10-05 14:18 | 2019-02-25 13:28 | MySQL Server: Group Replication | Closed (1886 days) | S2 | 5.7.23, 8.0.12 | Any | Any | Group Replication split brain with faulty network |
73725 | 2014-08-26 10:12 | 2014-10-21 19:06 | MySQL Server: Documentation | Closed (3474 days) | S2 | 5.6 5.7 | Any | Any | innodb_flush_log_at_trx_commit documented behavior much different since 5.6 |
98324 | 2020-01-22 9:57 | 2022-03-07 6:04 | MySQL Server: InnoDB storage engine | Verified (1485 days) | S2 | 5.7.26, 5.7.29, 8.0.20 | Any | Any | Deadlocks more frequent since version 5.7.26 |
72724 | 2014-05-22 19:19 | 2015-07-16 14:09 | MySQL Server: Installing | Closed (3206 days) | S2 | 5.6.17 | Linux | Any | mysql_install_db does not set up initial root user |
72322 | 2014-04-11 23:52 | 2015-06-23 14:09 | MySQL Server: Information schema | Closed (3271 days) | S2 | 5.5 5.6 5.7 | Any | Any | Query to I_S.tables and I_S.columns leads to huge memory usage |
95547 | 2019-05-27 14:37 | 2019-05-31 11:57 | MySQL Server: Replication | Verified (1791 days) | S2 | 5.7.26 | Any | Any | MySQL restarts automatically after ABORT_SERVER due to disk full |
71211 | 2013-12-23 9:21 | 2013-12-23 9:31 | MySQL Server: Archive storage engine | Verified (3776 days) | S2 | 5.1, 5.5, 5.6 | Any | Any | ARCHIVE engine does not guarantee UNIQUE and PRIMARY KEY constraints |
113440 | 2023-12-15 13:06 | 2024-01-03 6:17 | MySQL Server: InnoDB storage engine | Verified (130 days) | S2 | 8.0.35 | Any | Any | Table spaces with instant_col information can no longer be imported |
69825 | 2013-07-23 12:46 | 2013-08-06 14:37 | MySQL Server | Duplicate (3915 days) | S2 | 5.6.12 | Any | Any | InnoDB: Assertion failure in thread ... in file lock0wait.cc line 297 |
97913 | 2019-12-06 11:15 | 2019-12-23 5:55 | MySQL Server: InnoDB storage engine | Verified (1599 days) | S3 | 5.7.28 | Any | Any | Undo logs growing during partitioning ALTER queries |
101142 | 2020-10-12 22:49 | 2020-10-13 12:50 | MySQL Server: Logging | Not a Bug (1290 days) | S3 | 5.7.31, 8.0.20 | Any | Any | Queries long due to Lock_time not logged in the slow log |
102417 | 2021-01-29 9:54 | 2021-01-29 10:22 | MySQL Server: DDL | Verified (1182 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 (1121 days) | S3 | 8.0.23 | Any | Any | Inconsistent terminology change in error messages |
104099 | 2021-06-24 8:53 | 2021-08-26 23:04 | MySQL Server: Documentation | Closed (973 days) | S3 | 5.6, 5.7 | Any | Any | Replication and max_allowed_packet documentation incomplete for 5.6 and 5.7 |
104718 | 2021-08-25 9:59 | 2021-09-28 1:00 | MySQL Server: Documentation | No Feedback (941 days) | S3 | 8.0.25 | Any | Any | Documentation inaccurate about UPDATE_TIME in I_S.tables |
96853 | 2019-09-12 15:10 | 2019-09-19 10:19 | MySQL Server: Replication | Verified (1680 days) | S3 | 5.7.27 | Any | Any | Inconsistent super_read_only status when changing the variable is blocked |
114717 | 2024-04-20 18:57 | 2024-04-22 9:30 | MySQL Server: DDL | Verified (3 days) | S3 | 8.0.36 | Any | Any | Inconsistent behavior of explicit CHARSET/COLLATE column definition |
96644 | 2019-08-25 11:58 | 2019-09-13 10:03 | MySQL Server: Replication | Verified (1686 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 |
106012 | 2021-12-30 18:26 | 2022-04-06 11:48 | MySQL Server: InnoDB storage engine | Verified (751 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 (555 days) | S3 | 8.0, 5.7 | Any | Any | relay_log_space_limit VALID_RANGE improperly defined |
108532 | 2022-09-19 9:32 | 2022-09-19 9:42 | MySQL Server: Documentation | Verified (584 days) | S3 | 8.0.30 | Any | Any | Documentation missing redo log upgrade |
Showing 1-30 of 78 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |