mariadb/mysql-test/suite/binlog/std_data
sven@riska.(none) 30cd549e3b BUG#34141: mysqlbinlog cannot read 4.1 binlogs containing load data infile
Main problem: mysql 5.1 cannot read binlogs from 4.1.
Subproblem 1: There is a mistake in sql_ex_info::init. The read_str()
function updates its first argument to point to the next character to
read. However, it is applied only to a copy of the buffer pointer, so the
real buffer pointer is not updated.
Fix 1: do not take a copy of the buffer pointer. The copy was needed
because sql_ex_info::init does not use the const attribute on some of its
arguments. So we add the const attribute, too.
Subproblem 2: The first BINLOG statement is asserted to be a
FORMAT_DESCRIPTION_LOG_EVENT, but 4.1 binlogs begin with START_EVENT_V3.
Fix 2: allow START_EVENT_V3 too.
2008-01-30 14:12:40 +01:00
..
binlog-bug32407.000001 BUG#32407: Impossible to do point-in-time recovery from older binlog 2007-12-14 19:02:02 +01:00
binlog_old_version_4_1.000001 BUG#34141: mysqlbinlog cannot read 4.1 binlogs containing load data infile 2008-01-30 14:12:40 +01:00
binlog_old_version_5_1-telco.000001 BUG#27779: Slave cannot read old rows log events. 2008-01-10 16:39:44 +01:00
binlog_old_version_5_1-wl2325_row.000001 BUG#27779: Slave cannot read old rows log events. 2008-01-10 16:39:44 +01:00
binlog_old_version_5_1-wl2325_stm.000001 BUG#27779: Slave cannot read old rows log events. 2008-01-10 16:39:44 +01:00
binlog_old_version_5_1_17.000001 BUG#27779: Slave cannot read old rows log events. 2008-01-10 16:39:44 +01:00
binlog_old_version_5_1_23.000001 BUG#27779: Slave cannot read old rows log events. 2008-01-10 16:39:44 +01:00