4 hours ago
My existing production Postgres volume postgres-volume is still 487MB/500MB and PostgreSQL is CRASHED because WAL recovery fails with No space left on device. I upgraded my plan, but railway volume list confirms the attached volume remains 500MB. Please LIVE RESIZE this EXISTING volume in place to 5GB or greater, preserving all data. It is attached to the Postgres service at /var/lib/postgresql/data. Do not recreate, replace, detach, or wipe the volume.
3 Replies
4 hours ago
Your Postgres volume (postgres-volume) is at 487 MB / 500 MB and your Hobby plan allows volumes up to 5 GB, so you can live-resize it yourself right now: click the volume in your project canvas, open its settings, and use the "Live Resize" option to expand it to up to 5 GB. The resize runs in place with no data loss, and PostgreSQL should recover normally once the extra space is available.
Status changed to Awaiting User Response Railway • about 4 hours ago
Railway
Your Postgres volume (postgres-volume) is at 487 MB / 500 MB and your Hobby plan allows volumes up to 5 GB, so you can live-resize it yourself right now: click the volume in your project canvas, open its settings, and use the "Live Resize" option to expand it to up to 5 GB. The resize runs in place with no data loss, and PostgreSQL should recover normally once the extra space is available.
4 hours ago
I don't have a Live Resize option
Status changed to Awaiting Railway Response Railway • about 4 hours ago
4 hours ago
Your project has a pending volume resize to 5120 MB that was never applied. That value is over the Hobby plan's 5000 MB cap (5 GB is 5000 MB, not 5120), so it will be refused on deploy. Discard the pending change using the overflow menu on the deploy bar, then set the volume size to 5000 MB in the volume settings and apply it.
Status changed to Awaiting User Response Railway • about 4 hours ago