MDEV-35394 Innochecksum misinterprets freed undo pages #3636
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Innochecksum misinterprets the freed undo log pages as active one. This leads the user to think there are too many undo log pages exist.
Innochecksum can safely assume the undo log page is freed if the respective extent doesn't belong to a segment and marked as freed in XDES_BITMAP in extent descriptor page.
Innochecksum shouldn't assume that zero-filled page as extent descriptor page.
How can this PR be tested?
./mtr innodb.innochecksum_undo_page
Basing the PR against the correct MariaDB version
main
branch.PR quality check