mariadb/mysql-test/suite/binlog_in_engine/rpl_gtid_index.test
Kristian Nielsen fb41baad6c Binlog-in-engine: Disable test binlog_in_engine.rpl_gtid_index for Valgrind
The test requires large amounts of CPU and runs too slowly in Valgrind to
make sense, can even occasionally time out on loaded machines.

Signed-off-by: Kristian Nielsen <knielsen@knielsen-hq.org>
2026-01-29 12:52:24 +01:00

33 lines
939 B
Text

--source include/have_sequence.inc
--source include/have_innodb.inc
# Very CPU-intensive test, too slow to run in Valgrind.
--source include/not_valgrind.inc
--source include/master-slave.inc
--source include/have_binlog_format_mixed.inc
--let $binlog_in_engine_test= 1
--source suite/rpl/include/rpl_gtid_index_setup.inc
--echo *** A lot of GTIDs with small binlog size and state interval
--let $NUM_POS= 1000
--let $NUM_DOMAIN= 10
--let $NUM_SERVER= 5
--let $NUM_SLAVE_CONNECTS= 100
--let $RND_SEED= 150
--source suite/rpl/include/rpl_gtid_index.inc
--echo *** Switch to a larger binlog size
SET @old_binlog_size= @@GLOBAL.max_binlog_size;
SET GLOBAL max_binlog_size= 16*1024*1024;
--let $NUM_POS= 4000
--let $RND_SEED= 666
--source suite/rpl/include/rpl_gtid_index.inc
# Cleanup.
--connection master
SET GLOBAL max_binlog_size= @old_binlog_size;
--source suite/rpl/include/rpl_gtid_index_cleanup.inc
--source include/rpl_end.inc