21 days ago
Hi Railway team,
My hobby plan PostgreSQL service is in a crash loop due to a full disk volume. I accidentally uploaded a large video file through my app which stored it as a BYTEA blob directly in the database, filling the volume completely.
Error from logs:
FATAL: could not write to file "pg_wal/xlogtemp.41": No space left on device
The database keeps restarting but can't complete WAL recovery because it has no space to write.
What I need:
Could you either temporarily expand the volume by 1GB so I can connect and run DELETE FROM sops WHERE file_data IS NOT NULL; VACUUM FULL sops; — or run that query on my behalf? Once the large BYTEA data is cleared, the volume usage will drop back to normal and the service should recover fine.
Service details:
Project ID: d5fa0d27-eadb-4be1-bfe5-20261b775cef
Service ID: 4611ce43-9e6c-4902-9018-f0ded13c7ae4
Environment ID: 24720442-1117-4a1f-abea-d118aee34996
I'm on the hobby plan so I don't have access to backups or volume resizing. This was a one-time mistake and I've already fixed the app to not store files in Postgres going forward.
Thank you
1 Replies
21 days ago
Hobby plan users can resize volumes, so you can fix this yourself. Go to your Postgres volume settings and use Live Resize to expand from 500MB up to 5GB. Since the volume is at 100% capacity, the system will perform an offline resize with a brief restart, after which Postgres should complete WAL recovery and you can connect to clean up the data.
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