Bug #73582 Documentation says group commit for the binary log works only if sync_binlog=0
Submitted: 14 Aug 2014 12:18 Modified: 29 Sep 2014 16:48
Reporter: Przemyslaw Malkowski Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.6 5.7 OS:Any
Assigned to: David Moss CPU Architecture:Any
Tags: binary log, Group Commit

[14 Aug 2014 12:18] Przemyslaw Malkowski
Description:
We can read here:
http://dev.mysql.com/doc/refman/5.6/en/innodb-performance-group_commit.html
http://dev.mysql.com/doc/refman/5.7/en/innodb-performance-group_commit.html

"When the binlog is enabled, you typically also set the configuration option sync_binlog=0, because group commit for the binary log is only supported if it is set to 0."

However, we can see that the performance benefits from implementing group commit for the binary log in MySQL 5.6 apply for both sync_binlog=0 and sync_binlog=1:
https://blogs.oracle.com/MySQL/entry/mysql_5_6_replication_performance
http://mysqlmusings.blogspot.se/2012/06/binary-log-group-commit-in-mysql-56.html

How to repeat:
Compare documentation with official blog posts.

Suggested fix:
Make the documentation correct.
[14 Aug 2014 13:58] Umesh Shastry
Hello Przemyslaw,

Thank you for the report.

Thanks,
Umesh
[29 Sep 2014 16:48] David Moss
The documentation for version 5.6 and 5.7 was updated and the incorrect sentence removed. The changes are visible here:
http://dev.mysql.com/doc/refman/5.6/en/innodb-performance-group_commit.html
http://dev.mysql.com/doc/refman/5.7/en/innodb-performance-group_commit.html

For version 5.5:
http://dev.mysql.com/doc/refman/5.5/en/innodb-performance-group_commit.html
the sentence was modified to read:
When binary logging is enabled, to avoid synchronizing every transaction set sync_binlog=0.