mariadb/mysql-test/suite/binlog_in_engine/purge_locking.result
Kristian Nielsen 0ce6a9e22d Binlog-in-engine: Fix sporadic test failure of binlog_in_engine.purge_locking
The test was for some reason incorrectly doing SHOW BINLOG EVENTS when the
binlogging of the prior event is deliberately non-deterministic in which
binlog file it will appear in, causing test to depend on timing.

Signed-off-by: Kristian Nielsen <knielsen@knielsen-hq.org>
2026-02-01 12:31:39 +01:00

20 lines
678 B
Text

*** Test a binlog write running concurrently with a FLUSH BINARY LOGS.
include/reset_master.inc
CREATE TABLE t1(a INT PRIMARY KEY, b LONGBLOB) ENGINE=InnoDB;
connect con1,localhost,root,,;
SET SESSION debug_dbug= '+d,pause_binlog_write_after_release_page';
INSERT INTO t1 VALUES(0, REPEAT('#', 20000));
connection default;
FLUSH NO_WRITE_TO_BINLOG BINARY LOGS;
connection con1;
*** Now the same thing for RESET MASTER.
include/reset_master.inc
connection con1;
SET SESSION debug_dbug= '+d,pause_binlog_write_after_release_page';
INSERT INTO t1 VALUES(1, REPEAT('#', 20000));
connection default;
RESET MASTER;
connection con1;
connection default;
disconnect con1;
DROP TABLE t1;