mariadb/mysql-test/suite/binlog
unknown 0697ee265f MDEV-181: XID crash recovery across binlog boundaries
Keep track of how many pending XIDs (transactions that are prepared in
storage engine and written into binlog, but not yet durably committed
on disk in the engine) there are in each binlog.

When the count of one binlog drops to zero, write a new binlog checkpoint
event, telling which is the oldest binlog with pending XIDs.

When doing XA recovery after a crash, check the last binlog checkpoint
event, and scan all binlog files from that point onwards for XIDs that
must be committed if found in prepared state inside engine.

Remove the code in binlog rotation that waits for all prepared XIDs to
be committed before writing a new binlog file (this is no longer necessary
when recovery can scan multiple binlog files).
2012-06-22 11:46:28 +02:00
..
r MDEV-181: XID crash recovery across binlog boundaries 2012-06-22 11:46:28 +02:00
std_data Bug#47323 : mysqlbinlog --verbose displays bad output when events contain subset of columns 2009-10-09 16:54:48 +08:00
t MDEV-181: XID crash recovery across binlog boundaries 2012-06-22 11:46:28 +02:00
combinations WL#4350 Options in my.cnf style config file should not start with -- 2008-09-05 15:31:09 +02:00
disabled.def overlay support for mysql-test-run and mysqltest 2012-02-23 07:50:11 +01:00