Bug #48913 update table of options for innodb_flush_method
Submitted: 19 Nov 2009 16:43 Modified: 11 Jan 2010 19:54
Reporter: Lig Isler-Turmelle Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: Paul DuBois CPU Architecture:Any

[19 Nov 2009 16:43] Lig Isler-Turmelle
Description:
The permitted values graph on http://dev.mysql.com/doc/refman/5.1/en/innodb-parameters.html#sysvar_innodb_flush_method includes fdatasync when it should not after 5.1.24 as noted in the write up.

"Formerly it was possible to specify a value of fdatasync to obtain the default behavior. This is no longer possible as of MySQL 5.1.24 because it can be confusing that a value of fdatasync causes use of fsync() rather than fdatasync() for flushing."

Also a note on what value to give to get the default method is needed now that fdatasync is no longer available.  Is it an empty string, fsync or something else?  Clarification is needed.

How to repeat:
na

Suggested fix:
clarify and update the documentation.
[3 Dec 2009 3:54] Paul DuBois
Looks like the only way to get the default value not is to not specify innodb_flush_method at startup.

I tried these and they all failed:

innodb_flush_method
innodb_flush_method=
innodb_flush_method=''
innodb_flush_method=DEFAULT

Do you concur?
[8 Dec 2009 20:15] MySQL Verification Team
All said and done - I concur.
[4 Jan 2010 0:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[11 Jan 2010 19:54] Paul DuBois
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.