5 commits

Author	SHA1	Message	Date
Luis Soares	4cce928ea6	BUG#47014: rpl_drop_temp fails on PB-2 with results mismatch ... The test case creates two temporary tables, then closes the connection, waits for it to disconnect, then syncs the slave with the master, checks for remaining opened temporary tables on slave (which should be 0) and finally drops the used database (mysqltest). Unfortunately, sometimes, the test fails with one open table on the slave. This seems to be caused by the fact that waiting for the connection to be closed is not sufficient. The test needs to wait for the DROP event to be logged and only then synchronize the slave with the master and proceed with the check. This is caused by the asynchronous nature of the disconnect wrt binlogging of the DROP temporary table statement. We fix this by deploying a call to wait_for_binlog_event.inc on the test case, which makes execution to wait for the DROP temp tables event before synchronizing master and slave.	2009-09-13 21:52:14 +01:00
Alfranio Correia	831129493e	merge mysql-5.0-bugteam --> mysql-5.1-bugteam	2009-08-28 10:45:57 +01:00
skozlov/ksm@mysql.com/virtop.(none)	e9b8538fdc	WL#4091, enable rpl_flushlog_loop.test and fix for rpl_drop_temp.test	2008-03-01 00:05:23 +03:00
skozlov/ksm@mysql.com/virtop.(none)	3c108889fb	WL#4091, replace sleeps	2008-02-28 14:36:14 +03:00
msvensson@pilot.(none)	8661497e9b	WL#3933 Split main test suite to rpl, rpl_ndb and ndb ... - Update mysql-test-run.pl to collect tests from several suites - Group test into suites - Add suite.opt file	2007-06-27 14:28:02 +02:00

Renamed from mysql-test/t/rpl_drop_temp.test (Browse further)