a month ago
My Postgres-nMtu is stuck in a crashloop. Ideally I'd like to avoid loosing the data on it. I think it may be a WAL files issues.The PostgreSQL crash-looping with "No space left on device" on pg_wal, volume was resized from 1GB to 5GB but the resize isn't taking effect during recovery.
The details I have are: PostgreSQL 18.3 crash-looping. Recovery completes redo (1/2F41FDD0 to 1/38FFF6A8) but fails writing checkpoint: could not write to file "pg_wal/xlogtemp.33": No space left on device. Volume vol_ltoevpqgj8v9xvxc resized from 1GB to 5GB but mount still shows full. Hobby plan, no backups. Need WAL segments cleaned or volume force-remounted at new size.
Please can you either clear the WAL files or force-mount the new volume size?
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Hi pitesting, your Postgres service is currently showing as online in our system and running on a 20 GB volume, so it looks like you were able to work around this. If you'd still like us to expand any of your volumes to the size you originally requested, let us know which one and we'll take care of it.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 1 month ago