Moving block successors to their own table. #4296
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
clemahieu
force-pushed
the
sucessor_table
branch
from
6de90ff to
f198c8d
Compare
clemahieu
force-pushed
the
sucessor_table
branch
from
f198c8d to
2c5815c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When a new block is inserted, the previous block needs to be rewritten in order to update the sideband information which contains the block successor. This causes extra disk activity to copy and re-write the database page that contains the block.
This is a requirement in order to get the benefits from splitting the block table #4053.
This moves block successors out of block sideband and in to their own database table.