Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pma: fix regression on restore #224

Merged
merged 4 commits into from
Apr 4, 2024

Conversation

barter-simsum
Copy link
Contributor

There was a regression introduced with partition striping that caused problems on restore due to node partitions incidentally getting mapped anonymous rather than to the backing file

There was a regression introduced with partition striping that caused problems
on restore due to node partitions incidentally getting mapped anonymous rather
than to the backing file
@barter-simsum barter-simsum self-assigned this Mar 28, 2024
@barter-simsum
Copy link
Contributor Author

barter-simsum commented Mar 28, 2024

  • Awaiting testing from Rikard to see if this fixes the bt_sync bug he's encountering

There's no reason to initialize anything but the first metapage and it's
probably less error prone to leave the second metapage zeroed. On sync, the
first metapage will get memcpy'd to the second, so why partially write some of
the data now?
Copy link
Contributor

@ashelkovnykov ashelkovnykov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Paired w/ @barter-simsum to review. Looks correct to me, though I'm still novice to the PMA code.

@ashelkovnykov ashelkovnykov merged commit 06b62d3 into status Apr 4, 2024
1 check passed
@ashelkovnykov ashelkovnykov deleted the barter-simsum/pma-restore-regression-fix branch April 4, 2024 19:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants