Showing 1-30 of 79 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
84933 | 2017-02-10 3:22 | 2017-02-10 9:30 | MySQL Server: DML | Verified (2625 days) | S3 | 5.6 5.7, 5.6.35, 5.5.54 | Any | Any | same sql mode in 5.6 and 5.7 results in difference results |
87624 | 2017-08-31 11:04 | 2017-09-01 12:08 | MySQL Server: Replication | Verified (2422 days) | S2 | 5.6, 8.0.2, any?, 5.6.37 | Any | Any | Wrong statement-based binary logging for CONCAT() in stored procedure |
87560 | 2017-08-28 9:14 | 2021-04-19 4:25 | MySQL Server: XA transactions | Verified (2319 days) | S2 | mysql-5.7.17 | Any | Any | XA PREPARE log order error in replication and binlog recovery |
65923 | 2012-07-17 13:31 | 2017-01-20 10:04 | MySQL Server: Replication | Verified (4239 days) | S2 | 5.5.25a | Linux (Ubuntu 12.04 x86_64) | Any | Users and Privileges not replicated when binlog-ignore-db is used. |
87389 | 2017-08-11 7:30 | 2017-11-17 1:56 | MySQL Server: Replication | Verified (2433 days) | S3 | mysql-5.7.17 | Any | Any | Replication position not persisted correctly for XA transactions |
87385 | 2017-08-11 6:32 | 2017-11-17 1:55 | MySQL Server: Replication | Verified (2443 days) | S2 | mysql-5.7.17 | Any | Any | Partial external XA transactions are not rolled back correctly |
72457 | 2014-04-25 15:31 | 2018-09-27 14:41 | MySQL Server: Replication | Verified (3410 days) | S2 | 5.5.36, 5.6.23 | Linux | Any | Replication with no tmpdir space can break replication |
84630 | 2017-01-23 23:27 | 2017-03-13 13:02 | MySQL Server: Replication | Verified (2594 days) | S3 | 5.6.x, 5.7.x | Any | Any | override master variables with init_slave |
84996 | 2017-02-14 14:49 | 2017-02-16 16:56 | MySQL Server: InnoDB storage engine | Verified (2619 days) | S3 | 5.7.17 | Any | Any | Noisy InnoDB warnings maybe should not be there (or filterable) |
84998 | 2017-02-14 15:36 | 2017-02-15 8:02 | MySQL Server: Replication | Verified (2620 days) | S3 | 5.7+ | Any | Any | SHOW MASTER STATUS has no equivalent P_S table |
80400 | 2016-02-17 1:02 | 2018-02-08 22:54 | MySQL Server: Replication | Verified (2262 days) | S3 | 5.6.29, 5.6.31, 5.6.33, 5.7.20 | Fedora (23) | Any | semisync replication - STOP SLAVE SQL_THREAD - prevents master data modification |
84934 | 2017-02-10 4:23 | 2017-02-10 8:35 | MySQL Server: Replication | Verified (2625 days) | S3 | 5.7.17 | Any | Any | Column order is not important for replication to function |
84868 | 2017-02-07 20:26 | 2017-02-08 9:42 | MySQL Server: Replication | Verified (2627 days) | S3 | 5.7 | Any | Any | Please make it possible to query replication information consistently |
84247 | 2016-12-18 3:31 | 2016-12-19 5:13 | MySQL Server: Replication | Verified (2678 days) | S3 | 5.7, 5.7.17, 5.6.35 | Any | Any | Slave sql thread may quit with error 'Illegal mix of collations' |
83694 | 2016-11-04 18:06 | 2016-12-18 21:55 | MySQL Server: Replication | Verified (2690 days) | S3 | 5.6.34 | Ubuntu (16.04) | Any | Replication error 1236 - claims GTIDs purged on Master but are actually present! |
84185 | 2016-12-13 14:07 | 2016-12-14 7:20 | MySQL Server: Replication | Verified (2683 days) | S3 | 5.6, 5.7.17, 8.0.0, 5.6.35 | Any | Any | Not all "Statements writing to a table with an auto-increment..." are unsafe |
83749 | 2016-11-08 21:32 | 2016-12-07 3:32 | MySQL Server: Replication | Verified (2690 days) | S3 | 5.7.10 and onwards | Linux | Any | ERROR 1794 (HY000): Slave is not configured or failed to initialize properly |
84344 | 2016-12-27 8:29 | 2017-01-06 9:32 | MySQL Server: Replication | Verified (2660 days) | S3 | 5.7, 5.7.17 | Any | Any | ALTER USER with empty password replicates incorrectly |
83431 | 2016-10-18 18:53 | 2016-11-23 10:21 | MySQL Server: Row Based Replication ( RBR ) | Verified (2704 days) | S1 | 5.6.27.75, 5.6.34 | CentOS | Any | RBR slave's "BEGIN" binlog query event doesn't carry a session database name |
83158 | 2016-09-27 4:08 | 2018-08-17 4:41 | MySQL Server: Replication | Verified (2711 days) | S3 | MySQL 5.7 | Any | Any | Phantom-read problem in semi-sync loss-less replication |
101567 | 2020-11-11 19:22 | 2020-11-14 1:45 | MySQL Server: Replication | Verified (1253 days) | S2 | 5.7.30/5.7.31 | Any | Any | Generated column as primary key breaks replication |
113930 | 2024-02-08 11:41 | 2024-02-09 8:37 | MySQL Server: Performance Schema | Verified (70 days) | S3 | 8.0 | Any | Any | performance_schema_show_processlist = ON generates inconsistent output |
113236 | 2023-11-27 17:22 | 2024-02-03 15:05 | MySQL Server: Row Based Replication ( RBR ) | Verified (143 days) | S3 | 8.0.35-0ubuntu0.22.04.1 | Ubuntu (22.04.3 LTS 5.15.0-88-generic) | x86 (.) | conflicting replica_parallel_workers spec causes parallel_mode misconfig |
104546 | 2021-08-05 9:50 | 2024-01-30 15:57 | MySQL Server: Row Based Replication ( RBR ) | Verified (80 days) | S5 | 8.0.26 | Ubuntu (18.04.5 LTS) | x86 (Skylake-SP) | MySQL 8.0.26 single thread replication performance is slower than MySQL 5.7.35. |
113187 | 2023-11-22 16:24 | 2023-11-28 21:06 | MySQL Server: Replication | Verified (145 days) | S5 | 8.0 and above | Any | Any | replica SQL thread purge applied relay logs blocked commit on source node |
106818 | 2022-03-24 11:23 | 2022-06-07 2:29 | MySQL Server: Replication | Verified (682 days) | S2 | 5.7,8.0, 5.7.37 | Any | Any | Replication may fail when XA transactions use replace into statements |
107438 | 2022-05-31 19:57 | 2023-05-02 16:49 | MySQL Server: Replication | Verified (688 days) | S2 | 5.7.38 | CentOS (8) | Any | JSON STORED generated column values are inserted as NULL on replica |
106845 | 2022-03-26 13:23 | 2022-04-06 1:46 | MySQL Server: Replication | Verified (744 days) | S2 | 8.0.25 | CentOS (7.6) | ARM | Parallel replication not working with slave_preserve_commit_order=1 |
105300 | 2021-10-22 15:45 | 2021-10-22 16:04 | MySQL Server: Documentation | Verified (910 days) | S3 | Any | Any | Include newly added status_vars in QUERY_EVENT | |
105297 | 2021-10-22 15:09 | 2021-10-22 15:56 | MySQL Server: Documentation | Verified (910 days) | S3 | Any | Any | Correct length formula for null-bitmask field in table_map_event |
Showing 1-30 of 79 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |