2 months ago
My Postgres database crashed due to disk full (No space left on device on pg_wal). I resized the volume from 500MB to 5GB but the database is stuck in recovery and still can't start. I need help applying the volume resize so Postgres can complete WAL recovery.
2 Replies
2 months ago
Your Postgres service is in a crash loop where WAL recovery completes successfully but then fails writing to pg_wal because the volume filesystem still reports no space. The automatic restarts are restarting the process within the same container, so the volume resize from 500MB to 5GB is not being picked up. To apply the resize, you need to trigger a redeploy (not a restart) from the three-dot menu on the crashed deployment in the Deployments tab, which will create a new container with the expanded volume mounted.
Status changed to Awaiting User Response Railway • about 2 months ago
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Hey! It looks like your new Postgres service is running successfully with the full 5 GB volume. The volume resize is correctly applied and the service is healthy.
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