Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
Description
SHOW BINLOG EVENTS FROM <"random"-pos> caused a variety of failures as reported in MDEV-18046. They are fixed but that approach is not future-proof as well as is not optimal to create extra check for being constructed
event parameters.
The extra checks can and should be avoided with conduction validation
to the supplied offset. The validation means scan of the requested log
to find the requested position as one that points to the beginning of an event. Scanning is meaningful only to a non-default binlog-checksum-off files (that fact is captured by MDEV-18046).
Attachments
Issue Links
- relates to
-
MDEV-32628 Cryptic ERROR message & inconsistent behavior on incorrect SHOW BINLOG EVENTS FROM ...
-
- Closed
-
Hello Andrei,
Can you please review the fix for
MDEV-21839.Patch: https://github.com/MariaDB/server/commit/5bcf3104c94bfeeff2f9376b4d2065046b0e14de
Build Bot Testing: http://buildbot.askmonty.org/buildbot/grid?category=main&branch=bb-10.1-sujatha
Didn't add new tests as existing tests do the necessary testing:
binlog.binlog_show_binlog_event_random_pos
binlog.binlog_invalid_read_in_rotate