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

28 lines
1 KiB
Text

*** Test handling of disk full, waiting for space to be freed.
CREATE TABLE t1 (a INT NOT NULL, b INT NOT NULL, c LONGBLOB, PRIMARY KEY(a, b)) ENGINE=InnoDB;
INSERT INTO t1 VALUES (0, 0, 'Start');
INSERT INTO t1 VALUES (1, 0, REPEAT('a', 1000000));
connection default;
SET @old_dbug= @@GLOBAL.debug_dbug;
SET GLOBAL debug_dbug= '+d,ib_alloc_file_disk_full';
connect con1,localhost,root,,;
SET SESSION debug_dbug= '+d,dummy_keyword_just_to_not_enable_dbug_output';
SET SESSION debug_dbug= '-d,ib_alloc_file_disk_full';
INSERT INTO t1 VALUES (2, 0, REPEAT('b', 1000000));
connection default;
SELECT a, b, LENGTH(c) FROM t1 ORDER BY a, b;
a b LENGTH(c)
0 0 5
1 0 1000000
SET GLOBAL debug_dbug= @old_dbug;
connection con1;
connection default;
disconnect con1;
SELECT a, b, LENGTH(c) FROM t1 ORDER BY a, b;
a b LENGTH(c)
0 0 5
1 0 1000000
2 0 1000000
include/assert_grep.inc [Check that binlog pre-allocation is retried on ENOSPC]
DROP TABLE t1;
CALL mtr.add_suppression('InnoDB: Unable to allocate file.* "No space left on device"');