fix: restore-db.sh connects as the container's Coolify superuser, not "postgres" #71

Merged

dan-claude-bot merged 1 commit from fix/restore-db-superuser into main

2026-07-16 10:22:17 +00:00

Author	SHA1	Message	Date
claude-hdb	a51f0a0156	fix: restore-db.sh connects as the container's Coolify superuser, not "postgres" Coolify provisions each Postgres resource with a random POSTGRES_USER; the role "postgres" does not exist, so the hardcoded `psql -U postgres` fails with FATAL: role "postgres" does not exist. Surfaced by the Task 9 restore drill against box B. Expand $POSTGRES_USER inside the container (single-quoted sh -c) so the restore uses the resource's own superuser. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-07-15 21:02:57 +00:00

Author

SHA1

Message

Date

claude-hdb

a51f0a0156

fix: restore-db.sh connects as the container's Coolify superuser, not "postgres"

Coolify provisions each Postgres resource with a random POSTGRES_USER; the
role "postgres" does not exist, so the hardcoded `psql -U postgres` fails
with FATAL: role "postgres" does not exist. Surfaced by the Task 9 restore
drill against box B. Expand $POSTGRES_USER inside the container (single-quoted
sh -c) so the restore uses the resource's own superuser.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-07-15 21:02:57 +00:00