Replace unsafe hot-copy advice with sqlite3 online backup - #70
Merged
Merged
Conversation
A plain cp of the live SQLite file can capture a torn write, producing an unrestorable backup. Document .backup plus integrity_check on restore instead. Fixes #66
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.
What changes for operators?
Docs only: the production checklist no longer claims hot file copies are safe (they can tear mid-commit under rollback-journal mode). It now shows the online
.backupcommand, integrity check on restore, and volume-mount guidance.Failing-then-passing test
Docs fix — verified the documented procedure end to end locally (
.backup+integrity_check→ ok, row present). No fenced config blocks touched, so the README-validate gate is unaffected.Checklist
gofmt -l .clean (no Go changes)Fixes #66