Bug #83712 A mistake in the manual "18.4.1.34 Replication and Transaction Inconsistencies"

• Submitted: 7 Nov 2016 3:46
• Modified: 19 Jul 2017 12:04
• Reporter: huajun chen
• Status: Closed
• Category: MySQL Server: Documentation
• Severity: S3 (Non-critical)
• Version: 5.6,5.7
• OS: Any
• CPU Architecture: Any

[7 Nov 2016 3:46] huajun chen

Description:
The following description in the manual seems to be a mistake,

http://dev.mysql.com/doc/refman/5.7/en/replication-features-transaction-inconsistencies.ht...
----------------------------------------- 
Gap-free low-watermark position. Even in the absence of gaps, it is possible that transactions after Exec_master_log_pos have not been applied. 
----------------------------------------- 

Should the above "Exec_master_log_pos have not been applied" be "Exec_master_log_pos have been applied"? Please confirm it.

How to repeat:
always

[7 Nov 2016 5:22] MySQL Verification Team

Hello huajun chen,

Thank you for the report and feedback!

Thanks,
Umesh

[19 Jul 2017 12:04] Margaret Fisher

Posted by developer:
 
Thanks for reporting this. I see from the rest of the article that transactions after Exec_master_log_pos might or might not have been applied, but the important point in this paragraph is that they might have been applied.
I have changed the MySQL 5.7 and 8.0 documentation at
https://dev.mysql.com/doc/refman/5.7/en/replication-features-transaction-inconsistencies.h...
to read
Even in the absence of gaps, it is possible that transactions after Exec_master_log_pos have been applied.
The 5.6 documentation at https://dev.mysql.com/doc/refman/5.6/en/show-slave-status.html is okay.