feat(storage): consistent database backup via VACUUM INTO - #51
Merged
Conversation
- Store.Backup snapshots the live database without blocking writers, using SQLite's VACUUM INTO for a compact, standalone backup file - Atomic write (temp file + rename) with owner-only permissions - Backup is rejected inside transactions; mocks implement the new interface method - Add tests covering snapshot consistency, permissions, and tx rejection
…72,6089,6090,6091,6218})
This was referenced Aug 15, 2026
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
1 participant
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.
Phase 1 SQLite hardening (5/5). Merges after #50.
Store.Backup(ctx, path)snapshots the live database without blocking writers using SQLite'sVACUUM INTO(compact, standalone file)txStore/MockStorage/test mocks updated for the new interface methodMerge order: last in the sequence (after HNSW, #50).