MySQL Bugs: #77845: mysqldump adds SQL_LOG_BIN = 0 when --set-gtid-purged is enabled

Bug #77845	mysqldump adds SQL_LOG_BIN = 0 when --set-gtid-purged is enabled
Submitted:	27 Jul 2015 22:31	Modified:	12 Aug 2015 13:17
Reporter:	Jesper wisborg Krogh	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S2 (Serious)
Version:	5.6	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
In MySQL 5.6 and later when mysqldump is used to create a backup and --set-gtid-purged is enabled (this is the default if GTIDs are enabled), then it also adds a

   SET @@SESSION.SQL_LOG_BIN= 0;

(and associated statements to reset at the end).

This should be documented.

How to repeat:
See http://dev.mysql.com/doc/refman/5.6/en/mysqldump.html#option_mysqldump_set-gtid-purged

Suggested fix:
Add a note that binary logging is disabled if --set-gtid-purged is enabled.

Posted by developer:
 
Just to clarify as --set-gtid-purged can have three values:

--set-gtid-purged=OFF
  "SET @@SESSION.SQL_LOG_BIN= 0;" is never added
--set-gtid-purged=ON:
  "SET @@SESSION.SQL_LOG_BIN= 0;" is always added
--set-gtid-purged=AUTO:
  "SET @@SESSION.SQL_LOG_BIN= 0;" is added if GTIDs are enabled on the server you are backing up, i.e. if AUTO evaluates to ON.

Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly.