Bug #75032 | Don't write binlog position in trx_sys page if binlog_order_commits is disabled | ||
---|---|---|---|
Submitted: | 28 Nov 2014 5:18 | Modified: | 23 Mar 2020 21:15 |
Reporter: | zhai weixiang (OCA) | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 5.6, 5.7 | OS: | Any |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
[28 Nov 2014 5:18]
zhai weixiang
[23 Dec 2019 7:19]
MySQL Verification Team
Hi, Thanks for the report. Not reproduced yet, you are running a regular master-slave replication, right? thanks
[16 Feb 2020 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[12 Mar 2020 9:32]
zhai weixiang
I've checked the latest code of MySQL8.0.19. It looks like innodb doesn't store binlog position anymore unless clone is used. quoted code from function trx_write_serialisation_history: /* Update the latest MySQL binlog name and offset information in trx sys header only if MySQL binary logging is on and clone is has ensured commit order at final stage. */ if (Clone_handler::need_commit_order()) { trx_sys_update_mysql_binlog_offset(trx, mtr); } I'm afraid this will break functionity of backup tools which relies on the position.
[23 Mar 2020 21:15]
MySQL Verification Team
Hi Zhai, Yes, that's not related to the original report. If you can show the backup tool issue please create a separate bug report with a test case, I will appreciate that very much. best regards Bogdan