Showing 1-30 of 70 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
71211 | 2013-12-23 9:21 | 2013-12-23 9:31 | MySQL Server: Archive storage engine | Verified (3769 days) | S2 | 5.1, 5.5, 5.6 | Any | Any | ARCHIVE engine does not guarantee UNIQUE and PRIMARY KEY constraints |
112714 | 2023-10-13 12:45 | 2023-10-16 14:02 | MySQL Server: Clone Plugin | Can't repeat (188 days) | S3 | 8.0.34 | Any | Any | Assertion failure: clone0api.cc:1159:ib::fatal in cloning when undo_x_trunc.log |
72104 | 2014-03-23 0:22 | 2014-08-21 20:15 | MySQL Workbench | Closed (3528 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 (3163 days) | S3 | 5.5 5.6 5.7 | Any | Any | CHECKSUM TABLE results differ across MySQL versions |
113644 | 2024-01-15 14:13 | 2024-01-16 10:53 | MySQL Server: InnoDB storage engine | Verified (94 days) | S3 | 8.0 | Any | Any | Confusing thread id vs processlist id information in SEIS |
102395 | 2021-01-27 11:33 | 2021-01-27 12:18 | MySQL Server: DDL | Verified (1177 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 (698 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 (1478 days) | S2 | 5.7.26, 5.7.29, 8.0.20 | Any | Any | Deadlocks more frequent since version 5.7.26 |
108821 | 2022-10-19 10:01 | 2022-11-16 13:46 | MySQL Server: Documentation | Closed (519 days) | S3 | 8.0.31 | Any | Any | DOC issue with group_replication_communication_debug_options description |
104718 | 2021-08-25 9:59 | 2021-09-28 1:00 | MySQL Server: Documentation | No Feedback (934 days) | S3 | 8.0.25 | Any | Any | Documentation inaccurate about UPDATE_TIME in I_S.tables |
108532 | 2022-09-19 9:32 | 2022-09-19 9:42 | MySQL Server: Documentation | Verified (577 days) | S3 | 8.0.30 | Any | Any | Documentation missing redo log upgrade |
112670 | 2023-10-09 15:47 | 2023-10-10 5:04 | MySQL Server: Documentation | Verified (191 days) | S3 | 8.0.34 | Any | Any | Documentation outdated related ANALYZE TABLE locking |
73582 | 2014-08-14 12:18 | 2014-09-29 16:48 | MySQL Server: Documentation | Closed (3489 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 (3304 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 (1900 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 (1876 days) | S3 | 5.7.22, 8.0.12 | Any | Any | events_transactions_summary_global_by_event_name not working as expected |
109701 | 2023-01-19 11:11 | 2023-02-21 22:39 | MySQL Server: mysqldump Command-line Client | Duplicate (422 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 (323 days) | S3 | 8.0.32 | Any | Any | Fix for #33630199 in 8.0.32 not reflected in the documentation and release notes |
108824 | 2022-10-19 10:21 | 2022-10-19 10:52 | MySQL Server: Group Replication | Verified (547 days) | S3 | 8.0.31 | Any | Any | GCS_DEBUG_TRACE log not possible to rotate/archive without downtime |
92690 | 2018-10-05 14:18 | 2019-02-25 13:28 | MySQL Server: Group Replication | Closed (1879 days) | S2 | 5.7.23, 8.0.12 | Any | Any | Group Replication split brain with faulty network |
84574 | 2017-01-20 0:39 | 2017-02-09 12:53 | MySQL Server: Group Replication | Not a Bug (2625 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 (2330 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 (3102 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 (2327 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 (1673 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 (24 days) | S5 | 8.3.0, 8.0.36 | Any | Any | Inconsistent table performance: fresh data import vs after optimization |
103157 | 2021-03-30 22:01 | 2021-03-31 6:32 | MySQL Server: Replication | Verified (1114 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 (2031 days) | S3 | 5.7.23, 8.0.12 | Any | Any | information_schema.innodb_trx trx_is_read_only not set for all RO transactions |
112252 | 2023-09-04 16:20 | 2023-11-07 11:29 | MySQL Server: InnoDB storage engine | Analyzing (171 days) | S3 | 8.0.33, 8.0.34 | Any | Any | InnoDB page compression impacts checkpointing |
73725 | 2014-08-26 10:12 | 2014-10-21 19:06 | MySQL Server: Documentation | Closed (3467 days) | S2 | 5.6 5.7 | Any | Any | innodb_flush_log_at_trx_commit documented behavior much different since 5.6 |
Showing 1-30 of 70 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |