mirror of
https://github.com/MariaDB/server.git
synced 2025-01-17 04:22:27 +01:00
ba835f89ba
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. mysql-test/include/cleanup_fake_relay_log.inc: Added auxiliary file to restore things that setup_fake_relay_log.inc did. mysql-test/include/setup_fake_relay_log.inc: Added auxiliary file to setup replication from an existing relay log. mysql-test/std_data/bug40482-bin.000001: Binlog file for rpl.rpl_binlog_corruption mysql-test/suite/rpl/t/rpl_binlog_corruption.test: New test file. sql/log_event.cc: Check that the incident number is correct at the time the event is constructed. Do not assert it at the time it is printed. sql/log_event.h: Incident_log_event::is_valid() should verify that the incident number is valid. sql/rpl_constants.h: Incident numbers should be hard-coded, since they may appear in files.
16 lines
356 B
PHP
16 lines
356 B
PHP
# ==== 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
|
|
|
|
# Remove files.
|
|
remove_file $_fake_relay_log;
|
|
remove_file $_fake_relay_index;
|
|
--disable_query_log
|
|
eval SET @@global.relay_log_purge= $_fake_relay_log_purge;
|
|
--enable_query_log
|