2 months ago
My PostgreSQL service is stuck in a crash-recovery loop after running out of disk space. I resized the volume from 434MB to 5GB via the Railway dashboard, but the resize has not taken effect on the actual filesystem.
Evidence from df -h output inside the container:
/dev/zd33472 434M 424M 204K 100% /var/lib/postgresql/dataThe volume still shows 434MB despite the resize to 5GB. PostgreSQL fails on every startup with:
FATAL: could not write to file "pg_wal/xlogtemp.26": No space left on deviceProject: honest-cooperation Service: Postgres Volume: vol_lstgvq6ui09rxi6i
1 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Hey! Your volume resize to 5 GB didn't fully apply on our end. We've corrected it and redeployed your Postgres service. You should now have the full ~5 GB of disk space available, and PostgreSQL should start up normally.
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