Details
- 
    Task 
- 
    Status: Closed (View Workflow)
- 
    Major 
- 
    Resolution: Fixed
- 
    None
- 
        Q3/2025 Maintenance
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
 
-         
- relates to
- 
                    MDEV-37231 mariadb-binlog GTID --start/stop-position ignoring Server ID -         
- Open
 
-         
- 
                    MDEV-35664 Improve mariadb-binlog implementation for --stop-datetime parameter -         
- Open
 
-         
- split from
- 
                    MDEV-4989 Support for GTID in mysqlbinlog -         
- Closed
 
-         
- 
                    MDEV-27037 Mysqlbinlog should output a warning if EOF is found before its stop condition -         
- Closed
 
-