| Showing all 19 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 72804 | 2014-05-29 23:37 | 2017-01-13 12:56 | MySQL Server: Replication | Verified (3771 days) | S1 | 5.6 | Any | Any | BINLOG statement can no longer be used to apply Query events |
| 102945 | 2021-03-12 8:04 | 2021-09-06 6:58 | MySQL Server: Replication | Verified (1296 days) | S3 | mysql.5.7 | Any | Any | MTS fail due to ignore stop event when logical timestamp reset on new binary fil |
| 96932 | 2019-09-18 14:17 | 2019-10-14 16:34 | MySQL Utilities: Binlog Events | Verified (1828 days) | S3 | 5.7.27, 8.0.17 | Any | Any | DROP TRIGGER IF EXISTS sql not written in slave binary log |
| 87560 | 2017-08-28 9:14 | 2021-04-19 4:25 | MySQL Server: XA transactions | Verified (2498 days) | S2 | mysql-5.7.17 | Any | Any | XA PREPARE log order error in replication and binlog recovery |
| 85828 | 2017-04-06 9:34 | 2017-04-06 15:04 | MySQL Server: Replication | Verified (2749 days) | S3 | 8.0.1 | Any | Any | Rename 'expire_logs_days' |
| 83418 | 2016-10-18 0:46 | 2016-10-18 8:51 | MySQL Server: Row Based Replication ( RBR ) | Verified (2919 days) | S5 | 5.6, 5.6.34 | Any | Any | When binlog_row_image is MINIMAL, some updates queries logs redundant columns |
| 75205 | 2014-12-13 17:26 | 2015-01-27 20:00 | MySQL Server: XA transactions | Verified (3549 days) | S2 | 5.7.5-m15 | Any | Any | Master should write a LOST_EVENTS entry on xa commit after recovery. |
| 72679 | 2014-05-19 12:14 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (3743 days) | S3 | 5.6.17, 5.6.21 | Any | Any | Undocumented behavior when dumping mysql database using mysqldump utility |
| 41101 | 2008-11-28 15:31 | 2023-02-12 20:45 | MySQL Server: Replication | In progress (5650 days) | S2 | 5.0.67 | Any | Any | set storage_engine and set create_table are not written to the binlog |
| 62537 | 2011-09-25 16:58 | 2012-01-09 13:20 | MySQL Server: Replication | Verified (4673 days) | S3 | 5.5.20 | Any | Any | False "unsafe statement" log report |
| 70923 | 2013-11-15 16:59 | 2013-11-18 19:03 | MySQL Server: Replication | Verified (3984 days) | S2 | 5.5.34, 5.6.16 | Any | Any | Replication failure on multi-statement INSERT DELAYED queries |
| 64635 | 2012-03-13 13:21 | 2018-03-20 14:30 | MySQL Cluster: Cluster (NDB) storage engine | Verified (4593 days) | S2 | 7.2.4 | Any (MS Windows 2008 Datacenter/Hyper-v, Linux) | Any | 7.2.4 Windows MySQL cluster with InnoDB database crashes |
| 64139 | 2012-01-26 22:20 | 2021-09-05 20:45 | MySQL Cluster: Replication | Verified (4646 days) | S3 | mysql-cluster-gpl-7.2.2 | Any | Any | Duplicate INSERTs in binary log for NDB tables when binlog_format=STATEMENT |
| 62829 | 2011-10-19 18:58 | 2011-10-20 13:13 | MySQL Server: Replication | Verified (4744 days) | S2 | 5.1.57 | Any | Any | INSERT/SELECT between Blackhole tables loses INSERT_ID |
| 47228 | 2009-09-09 19:00 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (5514 days) | S2 | mysql-5.1-telco-7.0 | Any (tested on freebsd and linux) | Any | Incorrect conducting or loading binary logs |
| 46172 | 2009-07-14 15:17 | 2012-05-18 20:19 | MySQL Cluster: Replication | Verified | S2 | mysql-5.1 | Any | Any | row events in binlog when using ndb even if binlog_format=statement |
| 43398 | 2009-03-05 4:45 | 2016-10-16 20:45 | MySQL Server: Options | Verified (5702 days) | S3 | 4.1, 5.0, 5,1, 6.0 bzr | Any | Any | mysqld in --bootstrap mode still initialises its binlog |
| 75746 | 2015-02-03 12:30 | 2015-03-10 1:44 | MySQL Server: Replication | Verified (3507 days) | S3 | 5.6.16, 5.6.22 | Linux | Any | set log_bin_use_v1_row_events lead to corrupted row event |
| 78898 | 2015-10-21 13:04 | 2017-01-06 17:24 | MySQL Enterprise Backup | Verified (3281 days) | S2 | 3.12.1 | SUSE (SLE 11 SP3) | Any | mysqlbackup does not store binlog pos in log file |
| Showing all 19 (Edit, Save, CSV, Feed) |
