summaryrefslogtreecommitdiff
path: root/mysql-test/t/rpl_relayrotate.test
diff options
context:
space:
mode:
authorguilhem@gbichot2 <>2003-12-19 22:40:23 +0100
committerguilhem@gbichot2 <>2003-12-19 22:40:23 +0100
commitdf3b1a54f4cc62411b73ea8e146b9527147918db (patch)
tree708d0a5c519d1fb1a8117cc2a989a7c74fb8ac3f /mysql-test/t/rpl_relayrotate.test
parent2f3c1efaa73824447b81dc5461b747a8cd3fad2a (diff)
downloadmariadb-git-df3b1a54f4cc62411b73ea8e146b9527147918db.tar.gz
This is the final commit for Worklog tasks:
* A more dynamic binlog format which allows small changes (1064) * Log session variables in Query_log_event (1063) It contains a few bugfixes (which I made when running the testsuite). I carefully updated the results of the testsuite (i.e. I checked for every one, if the difference between .reject and .result could be explained). Apparently mysql-test-run --manager is broken in 4.1 and 5.0 currently, so I could neither run the few tests which require --manager, nor check that they pass nor modify their .result. But for builds, we don't run with --manager. Apart from --manager, the full testsuite passes, with Valgrind too (no errors). I'm going to push in the next minutes. Remains: update the manual. Note: by chance I saw that (in 4.1, in 5.0) rpl_get_lock fails when run alone; this is normal at it makes assumptions on thread ids. I will fix this one day in 4.1.
Diffstat (limited to 'mysql-test/t/rpl_relayrotate.test')
-rw-r--r--mysql-test/t/rpl_relayrotate.test4
1 files changed, 3 insertions, 1 deletions
diff --git a/mysql-test/t/rpl_relayrotate.test b/mysql-test/t/rpl_relayrotate.test
index 0e198d23517..64724061bc5 100644
--- a/mysql-test/t/rpl_relayrotate.test
+++ b/mysql-test/t/rpl_relayrotate.test
@@ -56,7 +56,9 @@ start slave;
# reading, MASTER_POS_WAIT() will do it for sure
# (the only statement with position>=3000 is COMMIT).
select master_pos_wait('master-bin.001',3000)>=0;
-select * from t1 where a=8000;
+select max(a) from t1;
+--replace_column 1 # 8 # 9 # 23 # 33 #
+show slave status;
# The following DROP is a very important cleaning task:
# imagine the next test is run with --skip-innodb: it will do