Details
-
Type:
Bug
-
Status: Confirmed
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: N/A
-
Fix Version/s: 10.1
-
Component/s: Scripts & Clients
-
Labels:None
Description
It's related to MDEV-6877 changes.
Test case (for reproducing, not for including into the test suite!)
# Run with --mysqld=--binlog-row-image=minimal --source include/have_log_bin.inc --source include/have_binlog_format_row.inc CREATE TABLE t1 (pk INT PRIMARY KEY, f1 INT, f2 INT, f3 INT, f4 INT, f5 INT, f6 INT, f7 INT, f8 INT); INSERT INTO t1 VALUES (10, 1, 2, 3, 4, 5, 6, 7, 8); DELETE FROM t1; --let $binlog = query_get_value(SHOW MASTER STATUS, File, 1) --let $datadir = `SELECT @@datadir` FLUSH BINARY LOGS; --exec $MYSQL_BINLOG --verbose --base64-output=DECODE-ROWS $datadir/$binlog DROP TABLE t1;
Partial output from 10.1 commit 302bf7c4664b904482ecc133476e822d497b114d
# at 739 #150705 2:12:29 server id 1 end_log_pos 777 GTID 0-1-3 /*!100001 SET @@session.gtid_seq_no=3*//*!*/; BEGIN /*!*/; # at 777 # at 827 #150705 2:12:29 server id 1 end_log_pos 827 Table_map: `test`.`t1` mapped to number 30 #150705 2:12:29 server id 1 end_log_pos 862 Delete_rows: table id 30 flags: STMT_END_F ### DELETE FROM `test`.`t1` ### WHERE ### @1=***Corrupted replication event was detected. Not printing the value*** # at 862 #150705 2:12:29 server id 1 end_log_pos 931 Query thread_id=4 exec_time=0 error_code=0 SET TIMESTAMP=1436051549/*!*/; COMMIT /*!*/; # at 931
Notes:
- FLUSH LOGS is unrelated, it just allows to avoid warnings;
- the number of fields seems to be important.
Gliffy Diagrams
Attachments
Issue Links
- relates to
-
MDEV-6877 Merge binlog_row_image from MySQL 5.6
-
- Closed
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions