2 months ago
Hi, I had a full database, I upgraded my subscription, I resized the database to 20 GB, but the database keeps crashing, can't restart, and I have no solution. Can you check the errors?
PostgreSQL Database directory appears to contain a database; Skipping initialization
2026-03-30 00:06:53.641 UTC [6] LOG: starting PostgreSQL 16.13 (Debian 16.13-1.pgdg13+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 14.2.0-19) 14.2.0, 64-bit
2026-03-30 00:07:13.379 UTC [30] FATAL: the database system is not yet accepting connections
2026-03-30 00:07:13.379 UTC [30] DETAIL: Consistent recovery state has not been yet reached.
2026-03-30 00:07:13.385 UTC [31] FATAL: the database system is not yet accepting connections
2026-03-30 00:07:13.385 UTC [31] DETAIL: Consistent recovery state has not been yet reached.
2026-03-30 00:07:13.394 UTC [32] FATAL: the database system is not yet accepting connections
2026-03-30 00:07:13.394 UTC [32] DETAIL: Consistent recovery state has not been yet reached.
2026-03-30 00:07:13.417 UTC [33] FATAL: the database system is not yet accepting connections
2026-03-30 00:07:13.417 UTC [33] DETAIL: Consistent recovery state has not been yet reached.
2026-03-30 00:07:14.393 UTC [34] FATAL: the database system is not yet accepting connections
2026-03-30 00:07:14.393 UTC [34] DETAIL: Consistent recovery state has not been yet reached.
2026-03-30 00:07:14.540 UTC [29] LOG: redo in progress, elapsed time: 20.07 s, current LSN: 6/BA099018
2026-03-30 00:07:15.614 UTC [35] FATAL: the database system is not yet accepting connections
2026-03-30 00:07:15.614 UTC [35] DETAIL: Consistent recovery state has not been yet reached.
2026-03-30 00:07:15.703 UTC [36] FATAL: the database system is not yet accepting connections
2026-03-30 00:07:15.703 UTC [36] DETAIL: Consistent recovery state has not been yet reached.
2026-03-30 00:07:16.625 UTC [37] FATAL: the database system is not yet accepting connections
2026-03-30 00:07:16.625 UTC [37] DETAIL: Consistent recovery state has not been yet reached.
2026-03-30 00:07:17.402 UTC [29] LOG: redo done at 6/C4FFFD60 system usage: CPU: user: 2.57 s, system: 2.95 s, elapsed: 22.93 s
2026-03-30 00:07:17.453 UTC [29] FATAL: could not write to file "pg_wal/xlogtemp.29": No space left on device
2026-03-30 00:07:17.467 UTC [6] LOG: startup process (PID 29) exited with exit code 1
2026-03-30 00:07:17.467 UTC [6] LOG: terminating any other active server processes
2026-03-30 00:07:17.476 UTC [6] LOG: shutting down due to startup process failure
2026-03-30 00:07:17.506 UTC [6] LOG: database system is shut down
2 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Hey! I took a look and the volume resize to 20 GB didn't fully apply on the backend. I've gone ahead and fixed that, and your Postgres service has been redeployed. You should now have ~19 GB of available disk space.
We've also shipped a fix to prevent this from happening on future volume resizes.
Status changed to Awaiting User Response Railway • about 2 months ago
brody
Hey! I took a look and the volume resize to 20 GB didn't fully apply on the backend. I've gone ahead and fixed that, and your Postgres service has been redeployed. You should now have ~19 GB of available disk space. We've also shipped a fix to prevent this from happening on future volume resizes.
2 months ago
Ok Brody.
Thank you so mutch
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Solved brody • about 2 months ago