2 months ago
Same issue as this thread — Postgres crash-looping with 'No space left on device' on pg_wal/xlogtemp. Volume shows 250GB but the resize didn't fully apply. The old disk size is still in effect. Can you correct this on your end like Brody did for the other user? Project: stackwatch, Postgres service
1 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
We investigated your Postgres volume and confirmed:
- Your volume resize to 250GB was applied successfully — the full 250GB is available
- Current disk usage is only ~6.5GB out of 229GB usable space (3%)
- Your Postgres service is currently running and healthy
The "No space left on device" errors on pg_wal/xlogtemp were transient while the resize was propagating. Your WAL recovery completed successfully and Postgres is now operating normally.
Your service should be fully operational. Let us know if you're still experiencing any issues.
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