Skip to content

Use database-wide eviction instead of per-table - #6586

Merged
joshua-spacetime merged 1 commit into
kim/local-tier-reclamationfrom
joshua/database-wide-eviction
Nov 16, 2026
Merged

joshua-spacetime merged 1 commit into
kim/local-tier-reclamationfrom
joshua/database-wide-eviction

Conversation

@joshua-spacetime

Copy link
Copy Markdown
Collaborator

Description of Changes

Before this change, if a transaction hit the memory limit, it would only try to evict pages only from the transaction-local set. If no pages/objects were evict-able, the transaction would fail. Now if no pages are evict-able, it will try to evict pages from committed set.

API and ABI breaking changes

N/A

Rollback safety impact

N/A

Expected complexity level and risk

2

Testing

Existing

@kim

kim commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

You beat me to it I guess: #6591

The issue with this patch is that it doesn't apply to the read path.
We may still want to go with it initially, as the full solution is substantially more complicated.

@joshua-spacetime
joshua-spacetime force-pushed the joshua/database-wide-eviction branch from ba2b45f to f33833a Compare November 16, 2026 16:56
@joshua-spacetime
joshua-spacetime merged commit 6786826 into kim/tiered-storage-integration Nov 16, 2026
55 of 63 checks passed
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