mariadb/mysql-test/suite/binlog
Kristian Nielsen 65353e1a40 Binlog-in-engine: mariabackup and concurrent FLUSH, PRUGE, or RESET MASTER
The mariabackup copies innodb-implemented binlog files at the end of the
backup. This does not need to block any writes to the binlogs, as the
--prepare will use the InnoDB redo to recover them into a consistent state.

However, the copy might complain about a file missing if PURGE BINARY
LOGS or RESET MASTER is run in parallel; or about a file changing size
if FLUSH BINARY LOGS is run in parallel. So prevent that by taking a
low-impact BACKUP STAGE START lock during the binlog copy, and
blocking on that in PURGE, RESET MASTER and FLUSH BINARY LOGS.

Signed-off-by: Kristian Nielsen <knielsen@knielsen-hq.org>
2025-10-23 23:31:52 +02:00
..
include Merge branch '10.11' into 11.4 2025-07-28 19:40:10 +02:00
r Binlog-in-engine: mariabackup and concurrent FLUSH, PRUGE, or RESET MASTER 2025-10-23 23:31:52 +02:00
std_data MDEV-30128 remove support for 5.1- replication events 2023-02-05 22:02:30 +01:00
t Binlog-in-engine: mariabackup and concurrent FLUSH, PRUGE, or RESET MASTER 2025-10-23 23:31:52 +02:00
combinations
disabled.def MDEV-30940: Revert "binlog.innodb_rc_insert_before_delete is disabled with MDEV-30490" 2023-01-30 21:28:21 +01:00
my.cnf MDEV-31404 Implement binlog_space_limit 2024-02-14 15:02:21 +01:00