a month ago
Hi, I had a full database, I upgraded my subscription, I resized the database to 10 GB, but the database keeps crashing, can't restart, and I have no solution. Can you check the errors?
2026-04-08 17:31:05.608 UTC [604] DETAIL: Consistent recovery state has not been yet reached.
Apr 8 2026 19:31:06
2026-04-08 17:31:05.639 UTC [605] FATAL: the database system is not yet accepting connections
Apr 8 2026 19:31:06
2026-04-08 17:31:05.639 UTC [605] DETAIL: Consistent recovery state has not been yet reached.
Apr 8 2026 19:31:06
2026-04-08 17:31:05.657 UTC [606] FATAL: the database system is not yet accepting connections
Apr 8 2026 19:31:06
2026-04-08 17:31:05.657 UTC [606] DETAIL: Consistent recovery state has not been yet reached.
Apr 8 2026 19:31:06
2026-04-08 17:31:05.660 UTC [30] FATAL: could not write to file "pg_wal/xlogtemp.30": No space left on device
Apr 8 2026 19:31:06
2026-04-08 17:31:05.671 UTC [7] LOG: startup process (PID 30) exited with exit code 1
Apr 8 2026 19:31:06
2026-04-08 17:31:05.671 UTC [7] LOG: terminating any other active server processes
Apr 8 2026 19:31:06
2026-04-08 17:31:05.672 UTC [7] LOG: shutting down due to startup process failure
Apr 8 2026 19:31:06
2026-04-08 17:31:05.698 UTC [7] LOG: database system is shut down
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Hey! The volume resize to 10GB didn't fully apply to the disk your Postgres was using — it was still seeing the old 5GB limit. We've fixed this on our end and redeployed your Postgres service. It should now have the full 10GB available and be starting up normally. Your data is intact.
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