| Showing 1-30 of 58 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 105962 | 2021-12-22 20:35 | 2021-12-23 5:02 | MySQL Server: InnoDB storage engine | Verified (228 days) | S4 | 8.0 | Any | Any | Add zstd as supported algorithm for InnoDB Page Compression |
| 84355 | 2016-12-28 10:06 | 2016-12-28 12:49 | MySQL Server: Options | Verified (2049 days) | S4 | 5.7 | Any | Any | Allow the secure_file_priv to accept more then one directory path |
| 71211 | 2013-12-23 9:21 | 2013-12-23 9:31 | MySQL Server: Archive storage engine | Verified (3150 days) | S2 | 5.1, 5.5, 5.6 | Any | Any | ARCHIVE engine does not guarantee UNIQUE and PRIMARY KEY constraints |
| 72104 | 2014-03-23 0:22 | 2014-08-21 20:15 | MySQL Workbench | Closed (2909 days) | S3 | 6.1.2, 6.0.9 | Linux | Any | Broken sorting of numeric columns |
| 73374 | 2014-07-24 11:15 | 2015-08-21 14:47 | MySQL Server | Closed (2544 days) | S3 | 5.5 5.6 5.7 | Any | Any | CHECKSUM TABLE results differ across MySQL versions |
| 102395 | 2021-01-27 11:33 | 2021-01-27 12:18 | MySQL Server: DDL | Verified (558 days) | S2 | 5.7.32, 8.0.23 | Any | Any | CREATE TABLE ... LIKE inconsistent behavior in regards to DATA DIRECTORY |
| 107293 | 2022-05-15 13:34 | 2022-05-21 20:52 | MySQL Server: Replication | Verified (79 days) | S2 | 5.7.37, 8.0.28 | Any | Any | CURRENT_TIMESTAMP not safe after all? |
| 98324 | 2020-01-22 9:57 | 2022-03-07 6:04 | MySQL Server: InnoDB storage engine | Verified (859 days) | S2 | 5.7.26, 5.7.29, 8.0.20 | Any | Any | Deadlocks more frequent since version 5.7.26 |
| 104718 | 2021-08-25 9:59 | 2021-09-28 1:00 | MySQL Server: Documentation | No Feedback (315 days) | S3 | 8.0.25 | Any | Any | Documentation inaccurate about UPDATE_TIME in I_S.tables |
| 73582 | 2014-08-14 12:18 | 2014-09-29 16:48 | MySQL Server: Documentation | Closed (2870 days) | S3 | 5.6 5.7 | Any | Any | Documentation says group commit for the binary log works only if sync_binlog=0 |
| 76566 | 2015-04-01 16:34 | 2015-04-02 7:30 | MySQL Server: InnoDB storage engine | Verified (2685 days) | S3 | 5.5 5.6, 5.5.44, 5.6.25 | Any | Any | Double transaction id for a DDL statements |
| 94187 | 2019-02-04 9:14 | 2019-02-05 5:44 | MySQL Server: Command-line Clients | Verified (1281 days) | S3 | 5.7.21 | Any | Any | Downgrade minor 5.7 version leaves incorrect innodb_table_stats schema |
| 92364 | 2018-09-11 12:06 | 2019-02-28 18:07 | MySQL Server: Performance Schema | Closed (1257 days) | S3 | 5.7.22, 8.0.12 | Any | Any | events_transactions_summary_global_by_event_name not working as expected |
| 92690 | 2018-10-05 14:18 | 2019-02-25 13:28 | MySQL Server: Group Replication | Closed (1260 days) | S2 | 5.7.23, 8.0.12 | Any | Any | Group Replication split brain with faulty network |
| 96931 | 2019-09-18 13:55 | 2019-09-19 6:51 | MySQL Server: Optimizer | Verified (1054 days) | S4 | 5.7, 8.0 | Any | Any | Implement max_rows_examined limit as another optimizer hint |
| 91697 | 2018-07-18 12:13 | 2020-03-04 14:13 | MySQL Server: InnoDB storage engine | Verified (887 days) | S4 | 5.7+ | Any | Any | Improve dedicated log file for InnoDB monitor |
| 84574 | 2017-01-20 0:39 | 2017-02-09 12:53 | MySQL Server: Group Replication | Not a Bug (2006 days) | S2 | 5.7.17 | Any | Any | In Group Replication, DDL execute on partitioned node leads to split brain |
| 88720 | 2017-11-30 14:52 | 2018-02-24 10:49 | MySQL Server: Replication | Verified (1711 days) | S3 | 5.6, 5.7, 8.0.3, 5.6.38, 5.7.20 | Any | Any | Inconsistent and unsafe FLUSH behavior in terms of replication |
| 78896 | 2015-10-21 10:32 | 2015-10-21 12:59 | MySQL Server: Errors | Verified (2483 days) | S3 | 5.7.8, 5.6.27, 5.6.28 | Any | Any | Inconsistent error on using view with missing definer |
| 84564 | 2017-01-19 13:56 | 2017-12-04 7:19 | MySQL Server: Replication | Duplicate (1708 days) | S2 | 5.7, 5.7.17 | Any | Any | Inconsistent GRANT behavior on master and slave breaks replication |
| 96853 | 2019-09-12 15:10 | 2019-09-19 10:19 | MySQL Server: Replication | Verified (1054 days) | S3 | 5.7.27 | Any | Any | Inconsistent super_read_only status when changing the variable is blocked |
| 103157 | 2021-03-30 22:01 | 2021-03-31 6:32 | MySQL Server: Replication | Verified (495 days) | S3 | 8.0.23 | Any | Any | Inconsistent terminology change in error messages |
| 92558 | 2018-09-25 12:02 | 2018-09-26 5:47 | MySQL Server: Information schema | Verified (1412 days) | S3 | 5.7.23, 8.0.12 | Any | Any | information_schema.innodb_trx trx_is_read_only not set for all RO transactions |
| 73725 | 2014-08-26 10:12 | 2014-10-21 19:06 | MySQL Server: Documentation | Closed (2848 days) | S2 | 5.6 5.7 | Any | Any | innodb_flush_log_at_trx_commit documented behavior much different since 5.6 |
| 69825 | 2013-07-23 12:46 | 2013-08-06 14:37 | MySQL Server | Duplicate (3289 days) | S2 | 5.6.12 | Any | Any | InnoDB: Assertion failure in thread ... in file lock0wait.cc line 297 |
| 85251 | 2017-03-01 13:16 | 2017-10-27 8:22 | MySQL Server: Replication | Closed (1774 days) | S2 | 5.7.17, 8.0.0 | Any | Any | Memory leak in master-master GTID replication with sync_relay_log_info |
| 85371 | 2017-03-08 10:46 | 2018-01-18 10:36 | MySQL Server: Replication | Closed (1718 days) | S2 | 5.7.17 | Any | Any | Memory leak in multi-source replication when binlog_rows_query_log_events=1 |
| 96400 | 2019-08-01 13:30 | 2022-06-15 21:07 | MySQL Server: Replication | Verified (1102 days) | S3 | 5.7.25, 5.7.27 | Any | Any | MTS STOP SLAVE takes over a minute when master crashed during event logging |
| 95547 | 2019-05-27 14:37 | 2019-05-31 11:57 | MySQL Server: Replication | Verified (1165 days) | S2 | 5.7.26 | Any | Any | MySQL restarts automatically after ABORT_SERVER due to disk full |
| 72724 | 2014-05-22 19:19 | 2015-07-16 14:09 | MySQL Server: Installing | Closed (2580 days) | S2 | 5.6.17 | Linux | Any | mysql_install_db does not set up initial root user |
| Showing 1-30 of 58 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
