alonso.torres c0cca0bf24 ⚡ Compact automatic file snapshots in a background task ...

An automatic snapshot taken by update-file stores the file data bytes as
they are, instead of realizing every objects-map and encoding the whole
file inside the request. When the data holds objects-maps, the new
compact-file-snapshot task, queued in the same transaction, rewrites the
snapshot with plain maps later. On the legacy-db backend the snapshot is
compacted inline.

fsnap/create! runs its writes in its own transaction, so callers that pass
only a pool (the restore backup) can queue the task. Whether stored bytes
hold objects-maps comes from the decoded data, not from the file features,
and compaction leaves pages behind a pointer unloaded.

2026-10-29 09:55:48 +01:00

..

backend_tests

⚡ Compact automatic file snapshots in a background task

2026-10-29 09:55:48 +01:00

e2e

🐛 Harden upload path handling and validation error bodies (#12067)

2026-10-17 16:01:04 +02:00