mariadb/mysql-test/suite/binlog_in_engine/binlog_restart.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

21 lines
734 B
Text

CREATE TABLE t1(a INT PRIMARY KEY, b INT, c LONGBLOB) ENGINE=InnoDB;
*** Test restarting the server on an existing binlog
include/reset_master.inc
SET SESSION binlog_annotate_row_events= 0;
INSERT INTO t1 VALUES (1, 0, REPEAT('@', 31760));
INSERT INTO t1 VALUES (2, 0, REPEAT('@', 100));
RESET MASTER;
INSERT INTO t1 VALUES (3, 0, REPEAT('&', 31760));
INSERT INTO t1 VALUES (4, 0, REPEAT('&', $length));
# restart
SELECT @@GLOBAL.max_binlog_size;
@@GLOBAL.max_binlog_size
262144
RESET MASTER;
INSERT INTO t1 VALUES (5, 0, REPEAT('@', 243700));
INSERT INTO t1 VALUES (6, 0, REPEAT('@', 100));
RESET MASTER;
INSERT INTO t1 VALUES (7, 0, REPEAT('&', 243700));
INSERT INTO t1 VALUES (8, 0, REPEAT('&', $length));
# restart
DROP TABLE t1;