mirror of
https://github.com/MariaDB/server.git
synced 2025-08-26 01:44:06 +03:00
cc05440836
Some of the test cases reference to binlog position and these position numbers are written into result explicitly. It is difficult to maintain if log event format changes. There are a couple of cases explicit position number appears, we handle them in different ways A. 'CHANGE MASTER ...' with MASTER_LOG_POS or/and RELAY_LOG_POS options Use --replace_result to mask them. B. 'SHOW BINLOG EVENT ...' Replaced by show_binlog_events.inc or wait_for_binlog_event.inc. show_binlog_events.inc file's function is enhanced by given $binlog_file and $binlog_limit. C. 'SHOW SLAVE STATUS', 'show_slave_status.inc' and 'show_slave_status2.inc' For the test cases just care a few items in the result of 'SHOW SLAVE STATUS', only the items related to each test case are showed. 'show_slave_status.inc' is rebuild, only the given items in $status_items will be showed. 'check_slave_is_running.inc' and 'check_slave_no_error.inc' and 'check_slave_param.inc' are auxiliary files helping to show running status and error information easily.
24 lines
656 B
Plaintext
24 lines
656 B
Plaintext
# This test checks that a slave DOES execute queries originating
|
|
# from itself, if running with --replicate-same-server-id.
|
|
|
|
source include/master-slave.inc;
|
|
connection slave;
|
|
create table t1 (n int);
|
|
reset master;
|
|
# replicate ourselves
|
|
stop slave;
|
|
--replace_result $SLAVE_MYPORT SLAVE_PORT
|
|
eval change master to master_port=$SLAVE_MYPORT;
|
|
start slave;
|
|
insert into t1 values (1);
|
|
save_master_pos;
|
|
sync_with_master;
|
|
select * from t1; # check that indeed 2 were inserted
|
|
# We stop the slave before cleaning up otherwise we'll get
|
|
# 'drop table t1' executed twice, so an error in the slave.err
|
|
# (not critical).
|
|
stop slave;
|
|
drop table t1;
|
|
|
|
# End of 4.1 tests
|