mariadb/mysql-test/suite/binlog_in_engine/crash_safe_slave.result
Kristian Nielsen 7081f2a58e Binlog-in-engine: New binlog implementation integrated in InnoDB
Implement an improved binlog implementation that is integrated into
the storage engine. The new implementation is enabled with the
--binlog-storage-engine option. Initially the InnoDB storage engine
implements the binlog.

Integrating the binlog in the storage engine improves performance,
since it makes the InnoDB redo log the single source of truth and
avoids the need for expensive two-phase commit between binlog and
engine. It also makes it possible to disable durability (set
--innodb-flush-log-at-trx-commit=0) to further improve performance,
while still preserving the ability to recover the binlog and database
into a consistent state after a crash.

The new binlog implementation also greatly improves the internal
design and implementation of the binlog, and enables future
enhancements for replication.

This is a squash of the original 11.4-based patch series.

Signed-off-by: Kristian Nielsen <knielsen@knielsen-hq.org>
2026-01-23 03:21:03 +01:00

25 lines
789 B
Text

include/master-slave.inc
[connection master]
*** Test that slave doesn't get ahead of a non-durable master that crashes.
connection master;
SET GLOBAL innodb_flush_log_at_trx_commit= 0;
CREATE TABLE t1 (a INT PRIMARY KEY, b INT, c TEXT) ENGINE=InnoDB;
SELECT COUNT(*) FROM t1;
COUNT(*)
630
SET SESSION debug_dbug="+d,crash_dispatch_command_before";
SELECT 1;
Got one of the listed errors
connection master1;
connection server_1;
connection default;
connection master;
include/rpl_reconnect.inc
SET STATEMENT gtid_domain_id= 1 FOR INSERT INTO t1 VALUES (9, 9, 'extra');
include/save_master_gtid.inc
connection slave;
include/sync_with_master_gtid.inc
# Asserted this: Row count should match on master and slave (no extra rows on slave)
connection master;
DROP TABLE t1;
include/rpl_end.inc