mirror of
https://github.com/MariaDB/server.git
synced 2025-02-20 20:33:15 +01:00

- mariadb-dump utility performs logical backups by producing set of sql statements that can be executed. By enabling this no-autocommit option, InnoDB can load the data in an efficient way and writes the only one undo log for the whole operation. Only first insert statement undergoes bulk insert operation, remaining insert statement doesn't write undo log and undergoes normal insert code path.
26 lines
805 B
Text
26 lines
805 B
Text
--source include/not_embedded.inc
|
|
|
|
--echo #
|
|
--echo # MDEV-18702 mysqldump should use max_statement_time=0 and/or allow setting one
|
|
--echo #
|
|
|
|
CREATE DATABASE test1;
|
|
USE test1;
|
|
CREATE TABLE t1 (i INT);
|
|
INSERT INTO t1 VALUES (0);
|
|
LOCK TABLE t1 WRITE;
|
|
--echo timeout without t1 contents expected
|
|
--error 2
|
|
--exec $MYSQL_DUMP --max-statement-time=1 --skip-lock-tables --skip-comments test1 t1
|
|
SET @save_max_statement_time=@@max_statement_time;
|
|
SET GLOBAL max_statement_time=0.1;
|
|
--send UNLOCK TABLES;
|
|
--echo This would be a race condition otherwise, but default max_statement_time=0 makes it succeed
|
|
--exec $MYSQL_DUMP --no-autocommit=0 --skip-lock-tables --skip-comments test1 t1
|
|
--reap
|
|
SET GLOBAL max_statement_time=@save_max_statement_time;
|
|
DROP DATABASE test1;
|
|
|
|
--echo #
|
|
--echo # End of 10.3 test
|
|
--echo #
|