PostgreSQL production database down. No space left after plan upgrade
coderyderx
PROOP

2 hours ago

Title: PostgreSQL crashed and won't restart after upgrading

My PostgreSQL database crashed because the disk was full. I upgraded my Railway plan, but it's still not working.

Every time I restart it, I get this error:

FATAL: could not write to file "pg_wal/xlogtemp.26": No space left on device

My entire n8n instance is down, and I can't access any of my workflows or run client automations.

I've already tried restarting PostgreSQL, but nothing has changed.

I need help getting the database running again without losing my workflows or data.

This is urgent. I'm paying for Railway to run client workflows, and everything is currently down. I'd appreciate help getting this resolved as soon as possible.

Awaiting User Response

3 Replies

Railway
BOT

2 hours ago

Your Postgres volume is still at its original 5 GB and is essentially full. Changing your plan raises how large a volume can be, but it does not grow volumes that already exist, so Postgres still has no room to write and crashes on every restart. Your data is still on the volume.

To fix it, open the Postgres volume's settings, choose Live Resize, and pick a larger size. Your Pro plan allows volumes up to 1 TB. Because the volume is at full capacity, the resize may run offline, which restarts Postgres with a short period of downtime. Once there is free space, Postgres can start again and n8n can reconnect. See Live Resizing the volume for details.


Status changed to Awaiting User Response Railway • about 2 hours ago


Railway

Your Postgres volume is still at its original 5 GB and is essentially full. Changing your plan raises how large a volume can be, but it does not grow volumes that already exist, so Postgres still has no room to write and crashes on every restart. Your data is still on the volume. To fix it, open the Postgres volume's settings, choose `Live Resize`, and pick a larger size. Your Pro plan allows volumes up to 1 TB. Because the volume is at full capacity, the resize may run offline, which restarts Postgres with a short period of downtime. Once there is free space, Postgres can start again and n8n can reconnect. See [Live Resizing the volume](https://docs.railway.com/volumes) for details.

coderyderx
PROOP

2 hours ago

where is the live resize? can't see it


Status changed to Awaiting Railway Response Railway • about 2 hours ago


Railway
BOT

2 hours ago

Live Resize sits in the volume's own settings, not in the Postgres service's settings. On your project canvas, click the volume attached to Postgres (postgres-volume, mounted at /var/lib/postgresql/data) to open it, go to its settings, and click Live Resize, then follow the prompts to pick a larger size. Your Pro plan allows up to 1 TB.

The volume is still at 5 GB with about 4.9 GB used. Because it is full, the resize may run offline, which restarts Postgres with a short period of downtime. Your data stays on the volume through the resize. See Live Resizing the volume for screenshots of the control.


Status changed to Awaiting User Response Railway • about 2 hours ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...