Postgres crash loop: No space left on device during WAL recovery
t1m0t
PROOP

2 months ago

Mon PostgreSQL est coincé dans une boucle de crash avec :

the database system is not yet accepting connections

2026-03-25 15:39:32.010 UTC [43] DETAIL: Consistent recovery state has not been yet reached.

2026-03-25 15:39:32.392 UTC [25] FATAL: could not extend file "base/16384/16801": No space left on device

2026-03-25 15:39:32.392 UTC [25] HINT: Check free disk space.

2026-03-25 15:39:32.392 UTC [25] CONTEXT: WAL redo at 4/5BAC1908 for Heap/INSERT+INIT: off: 1, flags: 0x00; blkref #0: rel 1663/16384/16801, blk 18131

2026-03-25 15:39:32.398 UTC [2] LOG: startup process (PID 25) exited with exit code 1

2026-03-25 15:39:32.398 UTC [2] LOG: terminating any other active server processes

2026-03-25 15:39:32.398 UTC [2] LOG: shutting down due to startup process failure

2026-03-25 15:39:32.411 UTC [2] LOG: database system is shut down

Projet : hearty-playfulness

Solved

2 Replies

Status changed to Awaiting Railway Response Railway about 2 months ago


2 months ago

Hi! Your volume resize to 150 GB didn't fully apply on the backend. We've corrected it and redeployed your Postgres service. You should now have the full ~150 GB of disk space available.

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


t1m0t
PROOP

2 months ago

Thank you Brody for your responsiveness and for the fix for the future resizing.


Status changed to Awaiting Railway Response Railway about 2 months ago


Status changed to Solved brody about 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...