mariadb/mysql-test/include/cleanup_fake_relay_log.inc

# ==== Purpose ====
#
# Clean up files create by setup_fake_relay_log.inc.
#
# ==== Usage ====
#
# See setup_fake_relay_log.inc

--echo Cleaning up after setup_fake_relay_log.inc

--disable_query_log
--disable_warnings
STOP SLAVE SQL_THREAD;
RESET SLAVE;
eval SET @@global.relay_log_purge= $_fake_relay_log_purge;
--enable_warnings
--enable_query_log
BUG#40482: server/mysqlbinlog crashes when reading invalid Incident_log_event Problem: When an Incident_log_event contains a bad incident number on disk, the server crashes with an assertion. Fix: Don't validate input with assertions. Use errors. 2008-12-29 17:04:10 +01:00			`# ==== Purpose ====`
			`#`
			`# Clean up files create by setup_fake_relay_log.inc.`
			`#`
			`# ==== Usage ====`
			`#`
			`# See setup_fake_relay_log.inc`

			`--echo Cleaning up after setup_fake_relay_log.inc`

			`--disable_query_log`
Bug#48308. 1. Now test use fake_relay_log primitive 2. Added RESET SLAVE to include/setup_fake_relay_log.inc for removing relay log info file 3. Added RESET SLAVE to include/cleanup_fake_relay_log.inc 4. Test moved to rpl suite as rpl_binlog_auto_inc_bug33029.test 5. Updated result file 2010-02-16 20:34:34 +01:00			`--disable_warnings`
			`STOP SLAVE SQL_THREAD;`
			`RESET SLAVE;`
BUG#40482: server/mysqlbinlog crashes when reading invalid Incident_log_event Problem: When an Incident_log_event contains a bad incident number on disk, the server crashes with an assertion. Fix: Don't validate input with assertions. Use errors. 2008-12-29 17:04:10 +01:00			`eval SET @@global.relay_log_purge= $_fake_relay_log_purge;`
Bug#48308. 1. Now test use fake_relay_log primitive 2. Added RESET SLAVE to include/setup_fake_relay_log.inc for removing relay log info file 3. Added RESET SLAVE to include/cleanup_fake_relay_log.inc 4. Test moved to rpl suite as rpl_binlog_auto_inc_bug33029.test 5. Updated result file 2010-02-16 20:34:34 +01:00			`--enable_warnings`
BUG#40482: server/mysqlbinlog crashes when reading invalid Incident_log_event Problem: When an Incident_log_event contains a bad incident number on disk, the server crashes with an assertion. Fix: Don't validate input with assertions. Use errors. 2008-12-29 17:04:10 +01:00			`--enable_query_log`