mirror of
https://github.com/MariaDB/server.git
synced 2025-07-02 14:22:51 +03:00
09c80e12c5
Major replication test framework cleanup. This does the following:
- Ensure that all tests clean up the replication state when they
finish, by making check-testcase check the output of SHOW SLAVE STATUS.
This implies:
- Slave must not be running after test finished. This is good
because it removes the risk for sporadic errors in subsequent
tests when a test forgets to sync correctly.
- Slave SQL and IO errors must be cleared when test ends. This is
good because we will notice if a test gets an unexpected error in
the slave threads near the end.
- We no longer have to clean up before a test starts.
- Ensure that all tests that wait for an error in one of the slave
threads waits for a specific error. It is no longer possible to
source wait_for_slave_[sql|io]_to_stop.inc when there is an error
in one of the slave threads. This is good because:
- If a test expects an error but there is a bug that causes
another error to happen, or if it stops the slave thread without
an error, then we will notice.
- When developing tests, wait_for_*_to_[start|stop].inc will fail
immediately if there is an error in the relevant slave thread.
Before this patch, we had to wait for the timeout.
- Remove duplicated and repeated code for setting up unusual replication
topologies. Now, there is a single file that is capable of setting
up arbitrary topologies (include/rpl_init.inc, but
include/master-slave.inc is still available for the most common
topology). Tests can now end with include/rpl_end.inc, which will clean
up correctly no matter what topology is used. The topology can be
changed with include/rpl_change_topology.inc.
- Improved debug information when tests fail. This includes:
- debug info is printed on all servers configured by include/rpl_init.inc
- User can set $rpl_debug=1, which makes auxiliary replication files
print relevant debug info.
- Improved documentation for all auxiliary replication files. Now they
describe purpose, usage, parameters, and side effects.
- Many small code cleanups:
- Made have_innodb.inc output a sensible error message.
- Moved contents of rpl000017-slave.sh into rpl000017.test
- Added mysqltest variables that expose the current state of
disable_warnings/enable_warnings and friends.
- Too many to list here: see per-file comments for details.
78 lines
2.6 KiB
Plaintext
78 lines
2.6 KiB
Plaintext
#############################################################################
|
|
# Original Author: JBM #
|
|
# Original Date: Aug/18/2005 #
|
|
#############################################################################
|
|
# TEST: To test the UUID() in rbr #
|
|
#############################################################################
|
|
|
|
# Begin clean up test section
|
|
connection master;
|
|
|
|
--disable_warnings
|
|
DROP PROCEDURE IF EXISTS test.p1;
|
|
DROP TABLE IF EXISTS test.t1;
|
|
--enable_warnings
|
|
|
|
# Section 1 test
|
|
|
|
eval CREATE TABLE test.t1 (a INT, blob_column LONGBLOB, vchar_column VARCHAR(100), PRIMARY KEY(a)) engine=$engine_type;
|
|
INSERT INTO test.t1 VALUES(1,UUID(),UUID());
|
|
delimiter |;
|
|
create procedure test.p1()
|
|
begin
|
|
INSERT INTO test.t1 VALUES(2,UUID(),UUID());
|
|
INSERT INTO test.t1 VALUES(3,UUID(),UUID());
|
|
end|
|
|
delimiter ;|
|
|
|
|
CALL test.p1();
|
|
|
|
# Now the same thing with a function
|
|
|
|
delimiter |;
|
|
create function test.fn1(x int)
|
|
returns int
|
|
begin
|
|
insert into t1 values (4+x,UUID(),UUID());
|
|
insert into t1 values (5+x,UUID(),UUID());
|
|
return 0;
|
|
end|
|
|
|
|
delimiter ;|
|
|
# test both in SELECT and in INSERT
|
|
select fn1(0);
|
|
eval create table t2 (a int) engine=$engine_type;
|
|
insert into t2 values(fn1(2));
|
|
|
|
sync_slave_with_master;
|
|
SHOW CREATE TABLE test.t1;
|
|
|
|
# Dump the databases and so we can see if they match
|
|
# Another method would be to use SELECT INTO OUTFILE on master,
|
|
# then LOAD DATA INFILE in slave, and use a query to compare.
|
|
# This would have the advantage that it would not assume
|
|
# the system has a 'diff'
|
|
--exec $MYSQL_DUMP --compact --order-by-primary --skip-extended-insert --no-create-info test > $MYSQLTEST_VARDIR/tmp/rpl_row_UUID_master.sql
|
|
--exec $MYSQL_DUMP_SLAVE --compact --order-by-primary --skip-extended-insert --no-create-info test > $MYSQLTEST_VARDIR/tmp/rpl_row_UUID_slave.sql
|
|
|
|
connection master;
|
|
# Let's cleanup
|
|
|
|
DROP PROCEDURE test.p1;
|
|
DROP FUNCTION test.fn1;
|
|
DROP TABLE test.t1;
|
|
DROP TABLE test.t2;
|
|
|
|
# Let's compare. Note: If they match test will pass, if they do not match
|
|
# the test will show that the diff statement failed and not reject file
|
|
# will be created. You will need to go to the mysql-test dir and diff
|
|
# the files your self to see what is not matching :-)
|
|
|
|
diff_files $MYSQLTEST_VARDIR/tmp/rpl_row_UUID_master.sql $MYSQLTEST_VARDIR/tmp/rpl_row_UUID_slave.sql;
|
|
|
|
# Cleanup dump files.
|
|
# Long-term "system rm" is not portable; we could live without
|
|
# this cleanup as no other test will use these files and they'll
|
|
# be removed at next testsuite run.
|
|
|