Bug #11825 | Clarify whether innodb_flush_log_at_trx_commit preserves crash-recovery | ||
---|---|---|---|
Submitted: | 8 Jul 2005 21:10 | Modified: | 5 Aug 2005 21:43 |
Reporter: | Kristian Nielsen | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S4 (Feature request) |
Version: | 5.0.8-beta-nightly-20050618 | OS: | N/A |
Assigned to: | Bugs System | CPU Architecture: | Any |
[8 Jul 2005 21:10]
Kristian Nielsen
[11 Jul 2005 11:40]
Heikki Tuuri
Assigning this to Jan Lindström. InnoDB's crash recovery does work regardless of the parameter value. Tables will not get corrupt in a crash. Setting it to != 1 can only cause some last transactions to be lost. Regards, Heikki
[11 Jul 2005 12:58]
Jan Lindström
InnoDB's crash recovery is not affected by the value but tables can be corrupted in the worst case if operating system or hardware fools that disk flush has been done but in reality it has not been done.
[5 Aug 2005 21:43]
Mike Hillyer
Jans changes are confirmed as present in the refman, closing bug.