mirror of
https://github.com/MariaDB/server.git
synced 2025-01-16 20:12:31 +01:00
f5c3e736f2
Problem was that with BINLOG-statement you can execute binlog events on master also (not only in applier). Fix removes too strict part wsrep_thd_is_applying from assertion. Note that actual event in test is intentionally corrupted to test should this error being ignored. Signed-off-by: Julius Goryavsky <julius.goryavsky@mariadb.com>
11 lines
740 B
Text
11 lines
740 B
Text
connection node_2;
|
|
connection node_1;
|
|
call mtr.add_suppression("BINLOG_BASE64_EVENT: Could not read field.*");
|
|
call mtr.add_suppression("BINLOG_BASE64_EVENT: Could not execute Write_rows_v1 event on table.*");
|
|
CREATE TABLE t1 (a INT NOT NULL AUTO_INCREMENT PRIMARY KEY, b INT, KEY(b)) engine=innodb;
|
|
BINLOG 'AMqaOw8BAAAAdAAAAHgAAAAAAAQANS42LjM0LTc5LjEtZGVidWctbG9nAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAEzgNAAgAEgAEBAQEEgAAXAAEGggAAAAICAgCAAAACgoKGRkAAYVx w2w=';
|
|
BINLOG 'wlZOTxMBAAAAKgAAADwCAAAAACkAAAAAAAEABHRlc3QAAnQxAAIDAwAC wlZOTxcBAAAAJgAAAGICAAAAACkAAAAAAAEAAv/8AgAAAAgAAAA=';
|
|
ERROR HY000: Got error 171 "The event was corrupt, leading to illegal data being read" from storage engine InnoDB
|
|
SELECT * FROM t1;
|
|
a b
|
|
DROP TABLE t1;
|