| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | WL#1717 "binlog/innodb consistency". | guilhem@mysql.com | 2004-06-23 | 1 | -0/+3 |
| | | | | | | | | | | 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. | ||||
| * | Robustness feature. | guilhem@mysql.com | 2004-06-20 | 1 | -0/+1 |
| | | | | | | | | | | | | | | | 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. | ||||
| * | Fixed that LOAD DATA INFILE works with transactions. | monty@hundin.mysql.fi | 2001-08-28 | 1 | -4015/+0 |
| | | | | | Fix for lower case filenames | ||||
| * | stop chewing! | sasha@mysql.sashanet.com | 2000-12-07 | 2 | -0/+5136 |
 |
index : delta/mariadb-git.git | |
| github.com: MariaDB/server.git |
| summaryrefslogtreecommitdiff |