Repository navigation
Conversation
kim
force-pushed
the
kim/page-manager
branch
17 times, most recently
from
October 7, 2026 15:03
d348a24 to
e53744a
Compare
Contributor
Author
|
Superseded by #6305 |
This file contains hidden or 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
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.
Description of Changes
Base machinery for tiered storage.
This doesn't really do anything yet, but changes page access to become fallible.
API and ABI breaking changes
Will change table access substantially.
Rollback safety impact
Intended to be rollback safe, as only internal APIs change.
Expected complexity level and risk
5
Testing
Not yet integrated, testing is in later PRs.