mirror of
https://github.com/MariaDB/server.git
synced 2025-01-19 13:32:33 +01:00
67ed422313
The reason of the bug is in that the test makes a trick with relay log files and did not reset fully at the end. If mtr does not restart the test the new SQL thread tried to work with the old time session data. Fixed with deploying RESET slave at the clean-up. mysql-test/suite/binlog/t/binlog_auto_increment_bug33029.test: adding RESET slave to force active mi and rli data struct to be reset. The slave SQL thread will deal with a fresh structures each time it restarts.
42 lines
582 B
Text
42 lines
582 B
Text
SET @old_relay_log_purge= @@global.relay_log_purge;
|
|
change master to
|
|
MASTER_HOST='dummy.localdomain',
|
|
RELAY_LOG_FILE='slave-relay-bin.000001',
|
|
RELAY_LOG_POS=4;
|
|
start slave sql_thread;
|
|
select MASTER_POS_WAIT('master-bin.000001', 3776);
|
|
# Result on slave
|
|
SELECT * FROM t1;
|
|
id
|
|
5
|
|
6
|
|
7
|
|
8
|
|
9
|
|
10
|
|
11
|
|
SELECT * FROM t2;
|
|
id
|
|
5
|
|
6
|
|
7
|
|
8
|
|
9
|
|
10
|
|
11
|
|
12
|
|
13
|
|
14
|
|
15
|
|
16
|
|
17
|
|
18
|
|
19
|
|
DROP TABLE IF EXISTS t1, t2;
|
|
DROP PROCEDURE IF EXISTS p1;
|
|
DROP PROCEDURE IF EXISTS p2;
|
|
DROP FUNCTION IF EXISTS f1;
|
|
DROP TRIGGER IF EXISTS tr1;
|
|
stop slave sql_thread;
|
|
reset slave;
|
|
SET @@global.relay_log_purge= @old_relay_log_purge;
|