Bug #85751 sql_log_bin documentation states that it can be set as a global variable
Submitted: 31 Mar 2017 17:42 Modified: 27 Jul 2017 12:06
Reporter: monty solomon Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.5, 5.6, 5.7 OS:Any
Assigned to: CPU Architecture:Any

[31 Mar 2017 17:42] monty solomon
Description:
The documentation for sql_log_bin states that is can be set as a global variable and provides warnings about changing it with global scope.

14.4.1.3 SET sql_log_bin Syntax
https://dev.mysql.com/doc/refman/5.7/en/set-sql-log-bin.html
https://dev.mysql.com/doc/refman/5.6/en/set-sql-log-bin.html
https://dev.mysql.com/doc/refman/5.5/en/set-sql-log-bin.html

As of MySQL 5.5, sql_log_bin can be set as a global or session variable. Setting sql_log_bin globally is only detected when a new session is started. Any sessions previously running are not impacted when setting sql_log_bin globally.

Warning
Incorrect use of sql_log_bin with a global scope means any changes made in an already running session are still being recorded to the binary log and therefore replicated. Exercise extreme caution using sql_log_bin with a global scope as the above situation could cause unexpected results including replication failure.

How to repeat:
mysql> SET GLOBAL sql_log_bin=0;
ERROR 1231 (42000): Variable 'sql_log_bin' can't be set to the value of '0'

mysql> SET GLOBAL sql_log_bin=1;
ERROR 1231 (42000): Variable 'sql_log_bin' can't be set to the value of '1'

Read the resolution of bug #67433.

The Server System Variables pages for versions 5.5, 5.6, and 5.7 were updated to reflect the change but the documentation page for setting sql_log_bin was not updated.

Suggested fix:
Update the documentation.
[1 Apr 2017 5:29] MySQL Verification Team
Hello Monty,

Thank you for the report and feedback.

Thanks,
Umesh
[27 Jul 2017 12:06] Paul DuBois
Posted by developer:
 
Updated, thanks.