21 days ago
myPostgres volume was 500 MB and hit 100% capacity, corrupting the database
ı 've expanded it to 5 GB, but Postgres is stuck in an infinite recovery loop: "could not write to file pg_wal/xlogtemp.50: No space left on device"
The database needs to be recovered from backup or manually repaired
Project ID: 37bbea8d-2ee0-4488-96db-620e3c18afbf
Volume ID: 866653d0-7868-4d39-8fa1-a553a63e5585
1 Replies
Status changed to Awaiting Railway Response Railway • 21 days ago
21 days ago
Your volume resize to 5 GB didn't apply - it hit a validation error at the plan-limit boundary, so the volume is still at 500 MB. We've resized it to 4 GB, which should give Postgres enough space to complete WAL recovery on its next restart. Our databases are unmanaged, so automatic snapshots, WAL recovery, and PITR aren't available unless you set up volume backups or PITR yourself. Going forward, upgrading to Pro unlocks native volume backups so your service can self-restore if this happens again.
Status changed to Awaiting User Response Railway • 21 days ago
14 days 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 • 14 days ago