1. 23 Jun, 2004 1 commit
    • guilhem@mysql.com's avatar
      WL#1717 "binlog/innodb consistency". · c267b19d
      guilhem@mysql.com authored
      Final push. Printing some warnings at startup, as --innodb-safe-binlog requires
      some other options, to work as expected.
      Adding 6 new tests (3 pairs). If they fail on some platforms (so far they have been run only on my Linux),
      they should be ignored for the 4.1.3 build (you can just
      rm mysql-test/*/rpl_crash_*).
      Now going to update doc.
      c267b19d
  2. 20 Jun, 2004 1 commit
    • guilhem@mysql.com's avatar
      Robustness feature. · f5d64244
      guilhem@mysql.com authored
      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.
      f5d64244
  3. 18 Jun, 2004 9 commits
  4. 17 Jun, 2004 12 commits
  5. 16 Jun, 2004 17 commits