2 months ago
I'm running n8n on Railway (Hobby plan). My PostgreSQL volume (night-volume) is at 100% capacity (5GB), causing Postgres to crash-loop.
Root cause: n8n's execution_entity table filled all storage. Postgres completes redo/recovery in ~30 seconds but then crashes with:
FATAL: could not write to file "pg_wal/xlogtemp.26": No space left on device
What I've tried:
- psql direct connection - fails (recovery mode)
- Railway CLI - fails
- Custom start commands to delete WAL files and TRUNCATE tables
- Pre-deploy commands with TRUNCATE
I do NOT want to wipe the volume - it contains important workflow data.
Is there any way to temporarily increase the volume without upgrading to Pro?
"I've seen Railway employees help with similar issues by running e2fsck and resize2fs on the volume filesystem. Could you please do the same for my volume? Project: robust-surprise, Volume: night-volume"
1 Replies
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
The Hobby plan volume limit is 5GB, which is where your volume currently sits, so live resize cannot increase it further on your current plan. To expand beyond 5GB, you would need to upgrade to the Pro plan, which supports volumes up to 50GB. Once upgraded, you can live resize the volume to give Postgres the space it needs to complete recovery and accept connections again.
Status changed to Awaiting User Response Railway • 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