PostgreSQL volume 100% full - service crashed, cannot connect
danilaejov
HOBBYOP

a month ago

Hi Railway team,

My PostgreSQL service (Postgres-_Dmw) in project dependable-empathy is down because the volume (vpn-service, 4.6GB) is at 100% capacity.

The issue is caused by n8n execution logs filling up the execution_entity table in the railway database. The service crashes immediately on startup and I cannot connect to run a DELETE query.

I need help with one of the following:

  1. Run DELETE FROM execution_entity; in the railway database on my behalf
  2. Clear the pg_wal directory to free up enough space for PostgreSQL to start
  3. Temporarily increase the volume size so I can clean it up myself

Project ID: 94b7481e-2b68-46e4-820e-d69a732cfb46

Environment: production

Service: Postgres-_Dmw (d50608a8-b9bb-47d1-973f-7d3140953bcb)

My data in smart_bets database is critical — please do not wipe the volume.

Thank you

Solved$10 Bounty

Pinned Solution

Try setting the custom start command to sleep infinity and redeploy.

5 Replies

Railway
BOT

a month ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway about 1 month ago


danilaejov
HOBBYOP

a month ago

@noahd Could you help with a similar issue? My PostgreSQL volume is at 100% and service cannot start. Would really appreciate a one-off bump like you did for the similar case.


You can go to the console tab by clicking in your service and run pg_resetwal from there.


0x5b62656e5d

You can go to the console tab by clicking in your service and run `pg_resetwal` from there.

danilaejov
HOBBYOP

a month ago

I cannot access the Console because the service crashes immediately on startup before I can connect. Could you please either:

  1. Run pg_resetwal /var/lib/postgresql/data on your side, or
  2. Do a one-off volume bump like @noahd did in the similar thread - just enough space to let PostgreSQL start so I can clean up the data myself.

Try setting the custom start command to sleep infinity and redeploy.


0x5b62656e5d

Try setting the custom start command to `sleep infinity` and redeploy.

danilaejov
HOBBYOP

a month ago

Thank you so much! The pg_resetwal and sleep infinity trick worked perfectly. Database is back online and all data is intact. Really appreciate the quick help!


Status changed to Open 0x5b62656e5d about 1 month ago


Status changed to Solved 0x5b62656e5d about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...