Showing all 19 (Edit, Save, CSV, Feed)
ID# Date Updated Type Status Sev Version OS CPU Summary
788982015-10-21
13:04
2017-01-06
17:24
MySQL Enterprise BackupVerified
(3329 days)
S23.12.1SUSE (SLE 11 SP3)Anymysqlbackup does not store binlog pos in log file
433982009-03-05
4:45
2016-10-16
20:45
MySQL Server: OptionsVerified
(5750 days)
S34.1, 5.0, 5,1, 6.0 bzrAnyAnymysqld in --bootstrap mode still initialises its binlog
411012008-11-28
15:31
2023-02-12
20:45
MySQL Server: ReplicationIn progress
(5698 days)
S25.0.67AnyAnyset storage_engine and set create_table are not written to the binlog
628292011-10-19
18:58
2011-10-20
13:13
MySQL Server: ReplicationVerified
(4792 days)
S25.1.57AnyAnyINSERT/SELECT between Blackhole tables loses INSERT_ID
625372011-09-25
16:58
2012-01-09
13:20
MySQL Server: ReplicationVerified
(4721 days)
S35.5.20AnyAnyFalse "unsafe statement" log report
709232013-11-15
16:59
2013-11-18
19:03
MySQL Server: ReplicationVerified
(4032 days)
S25.5.34, 5.6.16AnyAnyReplication failure on multi-statement INSERT DELAYED queries
728042014-05-29
23:37
2017-01-13
12:56
MySQL Server: ReplicationVerified
(3819 days)
S15.6AnyAnyBINLOG statement can no longer be used to apply Query events
834182016-10-18
0:46
2016-10-18
8:51
MySQL Server: Row Based Replication ( RBR )Verified
(2967 days)
S55.6, 5.6.34AnyAnyWhen binlog_row_image is MINIMAL, some updates queries logs redundant columns
757462015-02-03
12:30
2015-03-10
1:44
MySQL Server: ReplicationVerified
(3555 days)
S35.6.16, 5.6.22LinuxAnyset log_bin_use_v1_row_events lead to corrupted row event
726792014-05-19
12:14
2015-08-10
14:34
MySQL Server: mysqldump Command-line ClientVerified
(3791 days)
S35.6.17, 5.6.21AnyAnyUndocumented behavior when dumping mysql database using mysqldump utility
969322019-09-18
14:17
2019-10-14
16:34
MySQL Utilities: Binlog EventsVerified
(1876 days)
S35.7.27, 8.0.17AnyAnyDROP TRIGGER IF EXISTS sql not written in slave binary log
752052014-12-13
17:26
2015-01-27
20:00
MySQL Server: XA transactionsVerified
(3597 days)
S25.7.5-m15AnyAnyMaster should write a LOST_EVENTS entry on xa commit after recovery.
646352012-03-13
13:21
2018-03-20
14:30
MySQL Cluster: Cluster (NDB) storage engineVerified
(4641 days)
S27.2.4Any (MS Windows 2008 Datacenter/Hyper-v, Linux)Any7.2.4 Windows MySQL cluster with InnoDB database crashes
858282017-04-06
9:34
2017-04-06
15:04
MySQL Server: ReplicationVerified
(2797 days)
S38.0.1AnyAnyRename 'expire_logs_days'
461722009-07-14
15:17
2012-05-18
20:19
MySQL Cluster: ReplicationVerifiedS2mysql-5.1AnyAnyrow events in binlog when using ndb even if binlog_format=statement
472282009-09-09
19:00
2021-05-02
20:45
MySQL Cluster: Cluster (NDB) storage engineVerified
(5562 days)
S2mysql-5.1-telco-7.0Any (tested on freebsd and linux)AnyIncorrect conducting or loading binary logs
875602017-08-28
9:14
2021-04-19
4:25
MySQL Server: XA transactionsVerified
(2546 days)
S2mysql-5.7.17AnyAnyXA PREPARE log order error in replication and binlog recovery
641392012-01-26
22:20
2021-09-05
20:45
MySQL Cluster: ReplicationVerified
(4694 days)
S3mysql-cluster-gpl-7.2.2AnyAnyDuplicate INSERTs in binary log for NDB tables when binlog_format=STATEMENT
1029452021-03-12
8:04
2021-09-06
6:58
MySQL Server: ReplicationVerified
(1344 days)
S3mysql.5.7AnyAnyMTS fail due to ignore stop event when logical timestamp reset on new binary fil
Showing all 19 (Edit, Save, CSV, Feed)