docs: FAQ about chunker params for SQLite databases - #10162
Merged
ThomasWaldmann merged 1 commit intoAug 20, 2026
Conversation
ThomasWaldmann
force-pushed
the
sqlite-chunker-5877
branch
from
August 20, 2026 15:43
47377b3 to
eae8b30
Compare
ThomasWaldmann
force-pushed
the
sqlite-chunker-5877
branch
from
August 20, 2026 15:49
eae8b30 to
ed79f9d
Compare
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.
Adds a short FAQ entry (in "Usage & Limitations", next to the compression
question) recommending smaller chunks for SQLite database files.
It explains why the default ~2 MiB target chunk size is a bad fit for
in-place page updates, suggests
--chunker-params=fastcdc,15,19,17,2(~128 kiB target chunks) and the even finer
fastcdc,10,23,16,2, andnotes the resource cost plus the fact that chunker params apply per
borg createrun, so databases are best backed up in a separate run.Also mentions that borg copies the file as-is, so a live database may be
backed up in an inconsistent state.
Fixes #5877