2 months ago
i am getting same error even after the increase the disk size.
2026-03-23 16:51:59.831 UTC [29] LOG: redo done at 0/5CFFD248 system usage: CPU: user: 0.20 s, system: 0.11 s, elapsed: 4.27 s
2026-03-23 16:51:59.848 UTC [29] FATAL: could not write to file "pg_wal/xlogtemp.29": No space left on device
2026-03-23 16:51:59.857 UTC [3] LOG: startup process (PID 29) exited with exit code 1
2026-03-23 16:51:59.857 UTC [3] LOG: terminating any other active server processes
2026-03-23 16:51:59.860 UTC [3] LOG: shutting down due to startup process failure
2026-03-23 16:51:59.869 UTC [3] LOG: database system is shut down
2 Replies
2 months ago
Your pgvector service is in a crash loop where PostgreSQL attempts WAL recovery on each restart but fails with "No space left on device" before completing, which means the volume is still full. If a previous live resize failed, the volume settings will show a "Grow" button instead of "Live Resize", and the Grow operation requires a redeploy to take effect. Please check your volume settings to confirm whether the resize was applied, and if you have a backup available, that may be needed since the logs indicate repeated interrupted recovery attempts.
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
Your volume resize from 500 MB to 5 GB didn't fully apply on our end. We've corrected it and redeployed your pgvector service. You should now have approximately 4.6 GB of available disk space, which will give Postgres plenty of room for WAL recovery.
We've also shipped a fix to prevent this from happening on future volume resizes.
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