fix(release): make deployment backup and rollback immutable
This commit is contained in:
@@ -28,10 +28,11 @@ The restore smoke may only create databases whose name starts with
|
||||
use `pg_restore --clean` and drops the temporary database unless an operator
|
||||
explicitly asks to retain it.
|
||||
|
||||
Storage and model files are inventoried rather than copied into the database
|
||||
dump. Release backups must therefore be paired with the persistent storage
|
||||
volume backup policy. Use `--inventory-mode sha256` for final release
|
||||
evidence.
|
||||
Storage and model files are retained as byte-complete, SHA-256 verified
|
||||
snapshots alongside the database dump. Snapshot creation rejects symlinks and
|
||||
special files. The first snapshot uses CoW reflinks when supported and falls
|
||||
back to full copies; later snapshots hard-link checksum-identical files only
|
||||
from a verified older backup, never from live storage.
|
||||
|
||||
An old persistent volume can also retain glibc collation metadata for the
|
||||
empty `postgres` and `template1` system databases. If `createdb` fails for that
|
||||
|
||||
Reference in New Issue
Block a user