Bug #113243 The description of when to update the mysql.gtid_executed tabel is confusing
Submitted: 28 Nov 2023 3:01 Modified: 10 Dec 2023 0:27
Reporter: karry zhang (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:8.0 OS:Any
Assigned to: CPU Architecture:Any

[28 Nov 2023 3:01] karry zhang 
Description:
The documentation for MySQL 8.0 has the following description:

If binary logging is disabled (log_bin is OFF), or if log_replica_updates or log_slave_updates is disabled, the server stores the GTID belonging to each transaction together with the transaction in the mysql.gtid_executed table at transaction commit time.

This makes the reader think that the mysql.gtid_executed table is updated every time a transaction is committed.

However, we know that the corresponding gtid is only added to the buffer and is periodically written to the gtid_executed table by the background thread.

How to repeat:
This is a documentation issue, you can see it in https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-concepts.html.

Suggested fix:
I believe to make reader know the gtid is only add to the buffer is better.
[28 Nov 2023 5:00] MySQL Verification Team 
Hello karry zhang,

Thank you for the report and feedback.

regards,
Umesh
[10 Dec 2023 0:27] Jon Stephens 
Fixed in all versions of the Manual in mysqldoc rev 77456.

Closed.