Record each snapshot's uncompressed size when its backup runs (closes #360)
check / check (push) Canceled after 0s

snapshot list summed the chunks a snapshot reaches through its file rows
in the local index. A file's row is shared by every snapshot that lists
it and rewritten when the file changes, so backing up a changed file
changed every older snapshot's UNCOMPRESSED SIZE.

The backup now takes that total when it records the snapshot's stats,
into a new snapshots column, uncompressed_chunk_size, and snapshot list
reads the column, as it already does for new_chunk_size.

Model: opus-5-5
This commit was merged in pull request #366.
This commit is contained in:
2026-10-13 20:43:19 +02:00
parent fb8abcd049
commit 3361e9ebd9
6 changed files with 120 additions and 25 deletions
+2 -1
View File
@@ -294,7 +294,8 @@ needed.
of the local index and the backup destination store — with timestamps
and three sizes per snapshot (compressed remote size; total
uncompressed chunk size; size of the chunks that snapshot stored that
were not stored before, recorded when its backup ran).
were not stored before). Both chunk sizes are recorded when the
snapshot's backup runs.
Listing the destination store does **not** require the age secret key,
so it works in vaultik's intended configuration, where the backed-up