Bug #73725 innodb_flush_log_at_trx_commit documented behavior much different since 5.6
Submitted: 26 Aug 2014 10:12 Modified: 21 Oct 2014 19:01
Reporter: Przemyslaw Malkowski Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S2 (Serious)
Version:5.6 5.7 OS:Any
Assigned to: Daniel Price CPU Architecture:Any
Tags: doc innodb_flush_log_at_trx_commit

[26 Aug 2014 10:12] Przemyslaw Malkowski
Description:
In 
http://dev.mysql.com/doc/refman/5.5/en/innodb-parameters.html#sysvar_innodb_flush_log_at_t... 
we can read: 
"With a value of 2, an operating system crash or a power outage can erase the last second of commit records."

while in:
http://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#sysvar_innodb_flush_log_at_t...
and 
http://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb_flush_log_at_t...
we can see:
"With a value of 2, any mysqld process crash can erase up to a second of transactions."

Has this behavior seriously been changed or this is just documentation bug?

How to repeat:
Compare innodb_flush_log_at_trx_commit description for versions 5.5 and older versus 5.6+

Suggested fix:
Fix documentation or explain the difference.
[26 Aug 2014 11:43] Umesh Shastry
Hello Przemyslaw,

Thank you for the bug report.

Thanks,
Umesh
[21 Oct 2014 19:01] Daniel Price
This was a documented bug. There is no change in behaviour. The revised description should appear online within 24 hours.

Thank you for the bug report.
[21 Oct 2014 19:06] Daniel Price
Correction to my previous post: 

This was a *documentation* bug. There is no change in behaviour. The revised
description should appear online within 24 hours.