Commit 976b4e4
committed
postgres: change backup format from plain SQL to pg_dump custom
I'm experimenting with implementing the backup restore step and I ran
into a few complications:
* pg_restore does not like plain SQL and prefers this format they refer
to as "custom"
* psql does not allow us to change the role to `xsnippet-api` before
restoring the backup in an Ansible task, so all objects end up being
owned by the admin role `postgres`... And we can't use `become` because
the system user `xsnippet-api` does not exist at that point yet
Switching to the custom format allows us to have this symmetry between
pg_dump and pg_restore, and preserve/restore the correct owner value on
all database objects. pg_restore also allows to skip the commands
setting ownership, e.g. if we want to migrate to a different role.1 parent a8b2356 commit 976b4e4
1 file changed
+1
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
8 | 8 | | |
9 | 9 | | |
10 | 10 | | |
11 | | - | |
| 11 | + | |
12 | 12 | | |
0 commit comments