Repository navigation
Reclaim unused SQLite log database pages in the background - #49069
Merged
copyberry[bot] merged 1 commit intoSep 28, 2026
Conversation
## Why Deleting logs leaves free SQLite pages available for reuse without shrinking the database file. Reclaim excess free space while preserving a reserve for future writes. ## What changed - Start a background incremental-vacuum worker with `StateRuntime`, enabling reclamation only for the logs database. Use a per-home file lock to select one worker and wait for it to finish during shutdown. - Reclaim pages when at least 64 MiB and 25% of the database are free, preserving a reserve of at least 16 MiB or 10% of the database. - Use short transactions with page and cooperative time budgets, defer work on contention, and reduce batch sizes with exponential backoff when interrupted passes make no progress. - Record reclamation counts, durations, and reclaimed pages in telemetry. ## Testing Add a regression test that interrupts a vacuum commit, verifies foreground writes can resume without data loss, then confirms a resumed pass shrinks the database and passes `PRAGMA integrity_check`. GitOrigin-RevId: 8421f87b0aeef6540eda5690c84216906673c72e
copyberry
Bot
force-pushed
the
copyberry/codex-internal-to-codex-oss/8421f87b0aeef6540eda5690c84216906673c72e
branch
from
September 28, 2026 20:19
f9ee87b to
33a0f76
Compare
Contributor
|
I have read the CLA Document and I hereby sign the CLA You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot. |
copyberry
Bot
deleted the
copyberry/codex-internal-to-codex-oss/8421f87b0aeef6540eda5690c84216906673c72e
branch
September 28, 2026 20:19
kalinco-glitch
temporarily deployed
to
issue-triage
September 28, 2026 20:21 — with
GitHub Actions
Inactive
kalinco-glitch
temporarily deployed
to
issue-triage
September 28, 2026 20:21 — with
GitHub Actions
Inactive
kalinco-glitch
temporarily deployed
to
issue-triage
September 28, 2026 20:21 — with
GitHub Actions
Inactive
HSodergrenADI
temporarily deployed
to
issue-triage
September 28, 2026 20:23 — with
GitHub Actions
Inactive
HSodergrenADI
temporarily deployed
to
issue-triage
September 28, 2026 20:23 — with
GitHub Actions
Inactive
HSodergrenADI
temporarily deployed
to
issue-triage
September 28, 2026 20:23 — with
GitHub Actions
Inactive
brentjreynolds
temporarily deployed
to
issue-triage
September 28, 2026 20:24 — with
GitHub Actions
Inactive
brentjreynolds
temporarily deployed
to
issue-triage
September 28, 2026 20:24 — with
GitHub Actions
Inactive
brentjreynolds
temporarily deployed
to
issue-triage
September 28, 2026 20:24 — with
GitHub Actions
Inactive
This branch was previously deployed
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Reclaim unused SQLite log database pages in the background
Why
Deleting logs leaves free SQLite pages available for reuse without shrinking the database file. Reclaim excess free space while preserving a reserve for future writes.
What changed
StateRuntime, enabling reclamation only for the logs database. Use a per-home file lock to select one worker and wait for it to finish during shutdown.Testing
Add a regression test that interrupts a vacuum commit, verifies foreground writes can resume without data loss, then confirms a resumed pass shrinks the database and passes
PRAGMA integrity_check.