Repository navigation
Conversation
Tracks backing storage ownership in the page manager and blob set. After transactions and under memory budget pressure, orphaned objects are reclaimed.
Propagates TableCachePolicy::RequiredOnDisk by counting pin contributions on the backing ownership object introduced earlier.
kim
changed the base branch from
kim/local-tier-pinning-and-reclamation
to
kim/local-tier-pinning
November 13, 2026 17:03
kim
force-pushed
the
kim/local-tier-pinning
branch
4 times, most recently
from
November 16, 2026 14:06
9cb58b4 to
bf09241
Compare
Contributor
Author
|
Merged as 8ef39a0 |
kim
changed the base branch from
kim/local-tier-pinning
to
kim/tiered-storage-integration
November 17, 2026 10:49
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.
Bytesis often used in (tokio) networking code, and conversion fromBytestoArc<[u8]>involves copying (due to differing layout requirements).
So, just use
Bytes.We can revise to eliminate unnecessary copies that existed before.
API and ABI breaking changes
N/A
Rollback safety impact
N/A
Expected complexity level and risk
1
Testing
Both types are basically interchangeable, so no additional tests.