Bug #35366 | setting innodb_flush_log_at_trx_commit=1 also flushes after each second | ||
---|---|---|---|
Submitted: | 18 Mar 2008 6:29 | Modified: | 19 Mar 2008 9:59 |
Reporter: | Rizwan Maredia | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Logging | Severity: | S3 (Non-critical) |
Version: | 5.1.22 | OS: | Windows |
Assigned to: | CPU Architecture: | Any | |
Tags: | innodb_flush_log_at_trx_commit |
[18 Mar 2008 6:29]
Rizwan Maredia
[19 Mar 2008 9:59]
Sveta Smirnova
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://dev.mysql.com/doc/ and the instructions on how to report a bug at http://bugs.mysql.com/how-to-report.php According to http://dev.mysql.com/doc/refman/5.1/en/innodb-parameters.html#option_mysqld_innodb_flush_l...: "When this value is 1 (the default), the log buffer is written out to the log file at each transaction commit *and the flush to disk operation is performed on the log file.*" So it is expected to flush more often than transaction ends.
[19 Mar 2008 10:01]
Sveta Smirnova
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://dev.mysql.com/doc/ and the instructions on how to report a bug at http://bugs.mysql.com/how-to-report.php According to http://dev.mysql.com/doc/refman/5.1/en/innodb-parameters.html#option_mysqld_innodb_flush_l...: "When this value is 1 (the default), the log buffer is written out to the log file at each transaction commit *and the flush to disk operation is performed on the log file.*" So it is expected to flush more often than transaction ends.