Details
-
Task
-
Status: In Review (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
Description
In addition to MDEV-27037, which validates that a binlog coordinate or datetime based stop position actually exists within a binary log file provided to mariadb-binlog, 10.11 also supports GTID input to --stop-position, and this should also be validated that the given GTID exists within the input set of binary logs.
For more details, see the discussion on the MDEV-27037's PR here.
Attachments
Issue Links
- blocks
-
MDEV-35664 Improve mariadb-binlog implementation for --stop-datetime parameter
-
- Open
-
- is blocked by
-
MDEV-35528 mariadb-binlog cannot process more than 1 logfiles when --stop-datetime is specified
-
- Closed
-
- is caused by
-
MDEV-27037 Mysqlbinlog should output a warning if EOF is found before its stop condition
-
- Closed
-
- relates to
-
MDEV-35664 Improve mariadb-binlog implementation for --stop-datetime parameter
-
- Open
-
https://github.com/MariaDB/server/pull/3600