Bug #93544 | SHOW BINLOG EVENTS FROM <bad offset> is not diagnosed | ||
---|---|---|---|
Submitted: | 10 Dec 2018 14:39 | Modified: | 16 Jan 2019 15:34 |
Reporter: | Laurynas Biveinis (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 8.0.13 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | regression |
[10 Dec 2018 14:39]
Laurynas Biveinis
[11 Dec 2018 6:19]
MySQL Verification Team
Hello Laurynas, Thank you for the report. regards, Umesh
[16 Jan 2019 15:34]
Margaret Fisher
Posted by developer: Changelog entry added for MySQL 8.0.16: If an invalid starting offset was provided in a SHOW BINLOG EVENTS FROM statement, the invalid offset was returned in place of the correct starting position for the first returned event.