3 commits

Author	SHA1	Message	Date
unknown	0b8743c1b2	A fix for a random test failure rpl_trunc_binlog: don't RESET MASTER ... while the slave is connected. mysql-test/t/rpl_trunc_binlog.test: don't RESET MASTER while the slave is connected; this could confuse the master or slave. (In replication you don't RESET MASTER while a slave is connected!) sql/slave.cc: typo	2003-10-17 00:00:25 +02:00
unknown	654d266c8b	Fix for a test failure with the standard (no-BDB) binary: ... as the test is meaningful only if the slave supports transactions, we require this. As in 4.0 the slave runs with --skip-innodb, we test for BDB.	2003-10-07 20:41:06 +02:00
unknown	1bd7662b89	When the I/O thread was stopped while copying a long transaction, and restarted, ... Rotate_log_event::exec_event() believed that the relay log was corrupted. Fixed it by moving the test for corruption to Start_log_event::exec_event(). Changed Rotate_log_event::exec_event() to not increment positions when the event is seen in the middle of a transaction. I did a separate commit in 4.1 (so this should not be merged to 4.0) because code is a bit different in 4.1. A test to see if the slave detects when the master died while writing a transaction to the binlog (uses a forged truncated binlog I made). sql/log_event.cc: When the I/O thread was stopped while copying a long transaction, and restarted, Rotate_log_event::exec_event() believed that the relay log was corrupted. Fixed it by moving the test for corruption to Start_log_event::exec_event(). Changed Rotate_log_event::exec_event() to not increment positions when the event is seen in the middle of a transaction.	2003-10-03 22:13:01 +02:00