mariadb/mysql-test/suite/rpl
Luis Soares aaefb52df8 BUG#46166: MYSQL_BIN_LOG::new_file_impl is not propagating error
when generating new name.
      
If find_uniq_filename returns an error, then this error is not
being propagated upwards, and execution does not report error to
the user (although a entry in the error log is generated).
                  
Additionally, some more errors were ignored in new_file_impl:
- when writing the rotate event
- when reopening the index and binary log file
                  
This patch addresses this by propagating the error up in the
execution stack. Furthermore, when rotation of the binary log
fails, an incident event is written, because there may be a
chance that some changes for a given statement, were not properly
logged. For example, in SBR, LOAD DATA INFILE statement requires
more than one event to be logged, should rotation fail while
logging part of the LOAD DATA events, then the logged data would
become inconsistent with the data in the storage engine.
2010-11-30 23:32:51 +00:00
..
include Bug #49741 test files contain explicit references to bin/relay-log positions 2010-05-24 21:54:08 +08:00
r BUG#46166: MYSQL_BIN_LOG::new_file_impl is not propagating error 2010-11-30 23:32:51 +00:00
t BUG#46166: MYSQL_BIN_LOG::new_file_impl is not propagating error 2010-11-30 23:32:51 +00:00
combinations WL#4350 Options in my.cnf style config file should not start with -- 2008-09-05 15:31:09 +02:00
my.cnf Fix comment 2008-04-08 10:11:07 +02:00
README copy from test-extra-5.1 to main tree 2007-02-06 13:35:54 +01:00
rpl_1slave_base.cnf BUG#40257: Please remove --loose-skip-innodb from suite/rpl/rpl_1slave_base.cnf 2008-11-04 18:07:14 +01:00

How to run.
===========

./mysql-test-run.pl --suite=rpl --mysqld=--binlog-format=mixed