MySQL Bugs: #75393: Clarify the way the table mysql.gtid

Bug #75393	Clarify the way the table mysql.gtid_executed is updated.
Submitted:	2 Jan 2015 14:45	Modified:	21 Aug 2018 17:54
Reporter:	Jean-François Gagné	Email Updates:
Status:	Open	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S4 (Feature request)
Version:	5.7.5	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
Hi,

At the URL below, the description of the way the table mysql.gtid_executed  is updated can be found:

http://dev.mysql.com/doc/refman/5.7/en/replication-gtids-concepts.html#replication-gtids-g...

In summary, it says that:
-if log_bin is OFF, the table is updated for each transaction,
-if log_bin is ON, the table is updated when the binary log are rotated.

This does not describe the case of a slave with binary logging enabled, but with log-slave-updates disabled.  I tested that case and the behavior is as if binary logging was disabled (when the transactions are executed in the SQL Thread).

Could the documentation be updated accordingly ?

Thanks,

JFG

How to repeat:
Not exactly a bug, more a documentation change, see description.

There is no need to describe that behavior, since DMLs from SQL thread  will not go into binary log when that option is not enabled.

IMHO, what Sinisa wrote could be used as an argument to change a server behaviour, not to leave its documentation incomplete.

Related: Bug#92109.