a month ago
Hi team,
I'm currently facing a critical issue with my Postgres database. My disk got completely full, so I upgraded to the Pro plan and increased the volume size to 250GB. I also tried restoring a recent backup to get it running again.
However, the container keeps crashing almost instantly upon startup. I suspect that because the data is at 100% capacity, the database is crashing during the recovery/boot phase before your system has enough time to execute the volume resize script and recognize the new 250GB limit.
Here is the exact error log I am seeing in the panel right before it crashes:
2026-04-06 19:33:06.817 UTC [30] LOG: database system was not properly shut down; automatic recovery in progress
2026-04-06 19:33:06.835 UTC [30] LOG: redo starts at 0/22970C78
2026-04-06 19:33:14.247 UTC [30] LOG: redo done at 0/2AFFF6B0 system usage: CPU: user: 0.13 s, system: 0.31 s, elapsed: 7.41 s
2026-04-06 19:33:14.274 UTC [30] FATAL: could not write to file "pg_wal/xlogtemp.30": No space left on device
2026-04-06 19:33:14.285 UTC [6] LOG: startup process (PID 30) exited with exit code 1
2026-04-06 19:33:14.285 UTC [6] LOG: terminating any other active server processes
2026-04-06 19:33:14.286 UTC [6] LOG: shutting down due to startup process failure
2026-04-06 19:33:14.312 UTC [6] LOG: database system is shut down
Thank you for your help!
0 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Solved raulzitop • about 1 month ago