Postgres crashes on startup - volume full despite resize to 5GB
Anonymous
HOBBYOP

2 months ago

Hi, my Postgres service on Railway keeps crashing because the volume was 99% full (500MB limit from when I was on the Trial plan). I've since upgraded to Hobby and resized the volume to 5GB, but the old data is still filling up the disk so Postgres can't start.

The error in logs is: FATAL: could not write to file "pg_wal/xlogtemp": No space left on device

I need help, My workflow data in workflow_entity must be preserved.

MANY THANKS

Solved

9 Replies

Anonymous
HOBBYOP

2 months ago

URgent


Status changed to Awaiting Railway Response Railway about 2 months ago


Anonymous
HOBBYOP

2 months ago

urgent


vicnas
HOBBY

2 months ago

If I doesn't auto-crash, you could create a new and then migrate.


vicnas

If I doesn't auto-crash, you could create a new and then migrate.

Anonymous
HOBBYOP

2 months ago

sad thing....

it keeps auto-crash till now


Anonymous
HOBBYOP

2 months ago

need help


Anonymous
HOBBYOP

2 months ago

help


gadatos
PRO

2 months ago

could you please try the SHM fix (add RAILWAY_SHM_SIZE_BYTES=268435456 to your Postgres service and redeploy)


gadatos

could you please try the SHM fix (add RAILWAY\_SHM\_SIZE\_BYTES=268435456 to your Postgres service and redeploy)

Anonymous
HOBBYOP

2 months ago

Thanks gadatos,

tried it but still the same error: FATAL: could not write to file "pg_wal/xlogtemp.26": No space left on device

It seems the volume was resized to 5GB but the old data is still filling the disk.

Postgres can't complete recovery because it can't write WAL files.

LOL


Anonymous
HOBBYOP

2 months ago


Status changed to Solved brody about 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...