21 days ago
My PostgreSQL database has been down for over 1 hour in a crash recovery loop. I have expanded the volume from 500MB to 1GB (now 878 MiB available). The recovery is blocked by a recovery.signal file left from failed PITR attempts.
What I need: Please delete the file /var/lib/postgresql/data/pgdata/recovery.signal from my PostgreSQL container. With that file removed and sufficient disk space, PostgreSQL will complete normal crash recovery automatically.
Evidence from logs:
consistent recovery state reached at 1/90FFE918
redo done at 1/90FFE8E0
Disk is now 878 MiB (plenty of space)
The only blocker is the recovery.signal file requiring a restore_command that isn't configured
Pinned Solution
21 days ago
You can run commands in your postgres container from the Console tab, but you need to set the start command to sleep infinity to avoid postgres crashing the container. After you are done, remove the start command, and redeploy.
1 Replies
21 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 21 days ago
21 days ago
You can run commands in your postgres container from the Console tab, but you need to set the start command to sleep infinity to avoid postgres crashing the container. After you are done, remove the start command, and redeploy.
Status changed to Solved mayori • 21 days ago