-
Notifications
You must be signed in to change notification settings - Fork 68
[Do not merge] Add a garbage collector for old records #418
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
Open
somtochiama
wants to merge
11
commits into
main
Choose a base branch
from
somtochi/dumb-reaper
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
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
Signed-off-by: Somtochi Onyekwere <[email protected]>
Signed-off-by: Somtochi Onyekwere <[email protected]>
Signed-off-by: Somtochi Onyekwere <[email protected]>
Signed-off-by: Somtochi Onyekwere <[email protected]>
Signed-off-by: Somtochi Onyekwere <[email protected]>
gorbak25
reviewed
Feb 3, 2026
gorbak25
reviewed
Feb 3, 2026
gorbak25
reviewed
Feb 3, 2026
gorbak25
reviewed
Feb 3, 2026
Contributor
gorbak25
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Please add the tripwire so the reaper doesn't linger during tests/benchmarks.
Signed-off-by: Somtochi Onyekwere <[email protected]>
gorbak25
approved these changes
Feb 3, 2026
Signed-off-by: Somtochi Onyekwere <[email protected]>
Signed-off-by: Somtochi Onyekwere <[email protected]>
Signed-off-by: Somtochi Onyekwere <[email protected]>
Signed-off-by: Somtochi Onyekwere <[email protected]>
Signed-off-by: Somtochi Onyekwere <[email protected]>
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.
CR-SQLite, like most CRDT systems, retains metadata in clock tables for each primary key even after a row has been deleted. For tables where deleted rows are never re-inserted, this metadata can accumulate unnecessarily over time.
This pull request allows users to configure specific tables and a retention period, after which metadata associated with primary keys deleted before that period can be safely removed.
The catch here is that if these keys are re-inserted before all the nodes delete associated metadata, it could lead to some inconsistencies.So only enable this for tables wheree primary keys are never re-inserted after deletion.