2 months ago
My PostgreSQL database is stuck in a crash loop. It ran out of disk space during a WAL recovery operation. I resized the volume from 1GB to 5GB but the container filesystem did not expand — Postgres keeps failing at the same WAL position (0/43917F48) with "could not extend file base/16384/16689: No space left on device" on every restart.
The volume metrics show usage under 1GB with 5GB allocated, but the running container is not seeing the extra space.
I need either:
- Help forcing the filesystem to expand inside the container, OR
- Help skipping/clearing the WAL log so Postgres can start fresh
1 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Hey! The volume resize from 1 GB to 5 GB didn't fully apply on the backend. We've corrected this on our end and redeployed your Postgres service. You should now see ~5 GB of available disk space, and WAL recovery should complete successfully.
We've also shipped a fix to prevent this from happening on future volume resizes.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 2 months ago