Bug #68566 mysqlbinlog should be more friendly with GTID

• Submitted: 5 Mar 2013 0:50
• Modified: 20 Mar 2013 9:11
• Reporter: Yoshinori Matsunobu (OCA)
• Status: Verified
• Category: MySQL Server: Command-line Clients
• Severity: S4 (Feature request)
• Version: 5.6.10, 8.0
• OS: Any
• CPU Architecture: Any
• Tags: mysqlbinlog

[5 Mar 2013 0:50] Yoshinori Matsunobu

Description:
There are couple of use cases of parsing binary logs from GTID. At least following use cases can be considered.

1. --find-binlog-by-gtid=$GTID
- Input: GTID, multiple binlog files
- Output: Starting binlog filename and pos

2. --start-gtid=$GTID
- Input: GTID, multiple binlog files
- Output: all binary log events from the GTID

For example, when we want to analyze slaves' binary logs (based on master's file/pos and GTID), master file/pos are not correlated to slaves' file/pos so we need GTID to find the right position.

Apparently this should not be done in O(N), but implementation should be easy once http://bugs.mysql.com/bug.php?id=68386 is fixed.

How to repeat:
N/A

[20 Mar 2013 9:11] Luis Soares

Thank you for submitting this feature request.

[9 Apr 2018 18:07] Daniël van Eeden

The man page now lists this as synopsis:
mysqlbinlog [options] log_file ...

I think log_file should not be required when using:
--read-from-remote-master=BINLOG-DUMP-GTIDS
--exclude-gtids '<gtids>'

[6 Mar 2022 15:12] MySQL Verification Team

Bug #106646 marked as duplicate of this one