From f5d642448777999257f8c23dd25f2e9257912870 Mon Sep 17 00:00:00 2001
From: "guilhem@mysql.com" <>
Date: Sun, 20 Jun 2004 19:11:02 +0200
Subject: Robustness feature. Won't be pushed as is - separate email sent for
 internal review. WL#1717 "binlog-innodb consistency". Now when mysqld starts,
 if InnoDB does a crash recovery, we use the binlog name and position
 retrieved from InnoDB (corresponding to the last transaction successfully
 committed by InnoDB) to cut any rolled back transaction from the binary log.
 This is triggered by the --innodb-safe-binlog option. Provided you configure
 mysqld to fsync() InnoDB at every commit (using flush_log_at_trx_commit) and
 to fsync() the binlog at every write (using --sync-binlog=1), this behaviour
 guarantees that a master always has consistency between binlog and InnoDB,
 whenever the crash happens. 6 tests to verify that it works.

---
 mysql-test/misc/kill_master.sh | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 mysql-test/misc/kill_master.sh

(limited to 'mysql-test/misc')

diff --git a/mysql-test/misc/kill_master.sh b/mysql-test/misc/kill_master.sh
new file mode 100644
index 00000000000..e9bbf7542e7
--- /dev/null
+++ b/mysql-test/misc/kill_master.sh
@@ -0,0 +1 @@
+kill -9 `cat var/run/master.pid`
-- 
cgit v1.2.1