Bug #87660 mysql.gtid_executed table has nothing in it when disable binlog
Submitted: 5 Sep 2017 1:15 Modified: 22 Dec 2017 8:09
Reporter: aaron chan Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.7.17, 5.7.19 OS:CentOS
Assigned to: CPU Architecture:Any
Tags: gtid_executed

[5 Sep 2017 1:15] aaron chan 
Description:
when I disable binary logging and enable gtid mode , mysql.gtid_executed table has nothing in it and @@global.gtid_executed also is null. this is different from the document <https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-concepts.html> 

How to repeat:
as described above.
[5 Sep 2017 7:46] MySQL Verification Team 
Hello Aaron Chan,

Thank you for the report and feedback.
Discussed internally with Developer and concluded that it is a doc issue.

Thanks,
Umesh
[22 Dec 2017 8:09] Erlend Dahl 
[29 Nov 2017 5:53] Margaret Fisher

Thanks for the report. I have confirmed with development and updated the
documentation at
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-concepts.html
to clarify why this situation occurs. Changes should show online soon.