[MDEV-40674] Include the checksum for non-corrupted Unknown events - Jira

XML

Word

Printable

Details

Type: Technical task
Status: Closed (View Workflow)
Priority: Blocker
Resolution: Fixed
Affects Version/s: 10.11, 11.4
Fix Version/s: 10.11.19, 11.4.13, 11.8.9, 12.3.3, 13.0.2
Component/s: Replication, Scripts & Clients
Labels:

Sprint:
Q3/2026 Replic. Development

Description

Indeed, when the unknown is merely due to the type the checksum must be good (provided the arg is known to the client program).
And when the uknown is due to general corruption, even the --force mysqlbinlog would better off to stop at this event.
⸺ Elkin on Zulip

Attachments

Issue Links

includes

MDEV-40544 Assertion fail / Memory leak in `mariadb-binlog --force-read`

Closed

split to

MDEV-40759 `mariadb-binlog --force-read --start-position` crashes on Unknown event

Stalled

Activity

People

Assignee:: Jimmy Hú

Reporter:: Jimmy Hú

Assigned for Implementation:: Jimmy Hú

Assigned for Review:: Kristian Nielsen

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: 2026-08-07 23:29

Updated:: 2026-08-31 04:20

Resolved:: 2026-08-11 21:45

Time Tracking

Estimated:

0.75d

Remaining:

0d

Logged:

4h 20m

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.