Showing 1-30 of 43 (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 (3643 days) | S1 | 5.6.25, 5.6.26 | Any | Any | Transaction applied partially on a slave with relay_log_info_repository=table |
113440 | 2023-12-15 13:06 | 2024-01-03 6:17 | MySQL Server: InnoDB storage engine | Verified (579 days) | S2 | 8.0.35 | Any | Any | Table spaces with instant_col information can no longer be imported |
107293 | 2022-05-15 13:34 | 2022-05-21 20:52 | MySQL Server: Replication | Verified (1154 days) | S2 | 5.7.37, 8.0.28 | Any | Any | CURRENT_TIMESTAMP not safe after all? |
102395 | 2021-01-27 11:33 | 2021-01-27 12:18 | MySQL Server: DDL | Verified (1633 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 (1934 days) | S2 | 5.7.26, 5.7.29, 8.0.20 | Any | Any | Deadlocks more frequent since version 5.7.26 |
95547 | 2019-05-27 14:37 | 2019-05-31 11:57 | MySQL Server: Replication | Verified (2240 days) | S2 | 5.7.26 | Any | Any | MySQL restarts automatically after ABORT_SERVER due to disk full |
82599 | 2016-08-16 14:14 | 2025-02-11 18:04 | MySQL Server: Replication | Verified (3257 days) | S2 | 5.7.14,5.6, 5.6.32 | Any | Any | slave_type_conversions messing with data which still fits within allowed range |
71211 | 2013-12-23 9:21 | 2013-12-23 9:31 | MySQL Server: Archive storage engine | Verified (4225 days) | S2 | 5.1, 5.5, 5.6 | Any | Any | ARCHIVE engine does not guarantee UNIQUE and PRIMARY KEY constraints |
115563 | 2024-07-11 7:54 | 2024-07-16 6:53 | MySQL Server: Group Replication | Verified (367 days) | S3 | 8.0.38 | Any | Any | Group replication conflict resolutions seem inconsistent |
115062 | 2024-05-20 11:02 | 2024-05-20 15:05 | MySQL Server: Documentation | Verified (424 days) | S3 | 8.0 | Any | Any | Guidelines for estimating range optimization memory usage inaccurate |
114717 | 2024-04-20 18:57 | 2024-04-22 9:30 | MySQL Server: DDL | Verified (452 days) | S3 | 8.0.36 | Any | Any | Inconsistent behavior of explicit CHARSET/COLLATE column definition |
113644 | 2024-01-15 14:13 | 2024-01-16 10:53 | MySQL Server: InnoDB storage engine | Verified (550 days) | S3 | 8.0 | Any | Any | Confusing thread id vs processlist id information in SEIS |
103157 | 2021-03-30 22:01 | 2021-03-31 6:32 | MySQL Server: Replication | Verified (1570 days) | S3 | 8.0.23 | Any | Any | Inconsistent terminology change in error messages |
115954 | 2024-08-28 15:17 | 2024-08-29 9:09 | MySQL Server: Logging | Verified (323 days) | S3 | 8.4.2, 8.0.x | Any | Any | Confusing warning "Cannot add field x in table y because after adding it ..." |
112780 | 2023-10-20 10:05 | 2023-10-23 8:57 | MySQL Server: Documentation | Verified (634 days) | S3 | 8.0.34, 8.1.0 | Any | Any | innodb_temp_data_file_path changed from relative to absolute path in 8.0 |
112717 | 2023-10-13 15:14 | 2023-10-25 8:12 | MySQL Server: Replication | Verified (632 days) | S3 | 8.0.34 | Any | Any | Undo log truncation does not finalize when super_read_only=1 |
112705 | 2023-10-12 12:39 | 2023-10-12 12:53 | MySQL Server: SYS Schema | Verified (645 days) | S3 | 8.0.34 | Any | Any | sys.schema_table_statistics reset values upon index addition or removal |
112670 | 2023-10-09 15:47 | 2023-10-10 5:04 | MySQL Server: Documentation | Verified (647 days) | S3 | 8.0.34 | Any | Any | Documentation outdated related ANALYZE TABLE locking |
110117 | 2023-02-17 13:22 | 2023-02-17 15:32 | MySQL Server: Documentation | Verified (882 days) | S3 | 8.0 | Any | Any | Lack of instrumentation for index condition impact on the query plan |
116943 | 2024-12-11 13:50 | 2024-12-20 15:18 | MySQL Server: DDL | Verified (210 days) | S3 | 8.0.40 | Any | Any | Inconsistent metadata-only table and column collation changes behavior of ALTER TABLE |
108824 | 2022-10-19 10:21 | 2022-10-19 10:52 | MySQL Server: Group Replication | Verified (1003 days) | S3 | 8.0.31 | Any | Any | GCS_DEBUG_TRACE log not possible to rotate/archive without downtime |
108532 | 2022-09-19 9:32 | 2022-09-19 9:42 | MySQL Server: Documentation | Verified (1033 days) | S3 | 8.0.30 | Any | Any | Documentation missing redo log upgrade |
116944 | 2024-12-11 14:09 | 2024-12-11 14:24 | MySQL Server: Documentation | Verified (219 days) | S3 | 8.0, 8.4 | Any | Any | Documentation about online DDL missing collation changes |
94187 | 2019-02-04 9:14 | 2019-02-05 5:44 | MySQL Server: Command-line Clients | Verified (2356 days) | S3 | 5.7.21 | Any | Any | Downgrade minor 5.7 version leaves incorrect innodb_table_stats schema |
70202 | 2013-08-30 15:36 | 2013-09-02 11:53 | MySQL Server: DML | Verified (4337 days) | S3 | 5.5, 5.6 | Any | Any | REPLACE working differently for a table having PK or UK only versus both PK+UK |
76566 | 2015-04-01 16:34 | 2015-04-02 7:30 | MySQL Server: InnoDB storage engine | Verified (3760 days) | S3 | 5.5 5.6, 5.5.44, 5.6.25 | Any | Any | Double transaction id for a DDL statements |
77318 | 2015-06-11 14:40 | 2015-06-12 12:42 | MySQL Server: InnoDB storage engine | Verified (3689 days) | S3 | 5.5.44, 5.5.45 | Any | Any | Selects waiting on MDL when altering partitioned table |
78896 | 2015-10-21 10:32 | 2015-10-21 12:59 | MySQL Server: Errors | Verified (3558 days) | S3 | 5.7.8, 5.6.27, 5.6.28 | Any | Any | Inconsistent error on using view with missing definer |
88720 | 2017-11-30 14:52 | 2018-02-24 10:49 | MySQL Server: Replication | Verified (2786 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 |
89182 | 2018-01-11 9:51 | 2018-01-11 13:10 | MySQL Server: Optimizer | Verified (2745 days) | S3 | 5.6.38, 5.7.20, 8.0.3 | Any | Any | Optimizer unable to ignore index part entering less optimal query plan |
Showing 1-30 of 43 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |