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:
- Run
DELETE FROM execution_entity;in therailwaydatabase on my behalf - Clear the
pg_waldirectory to free up enough space for PostgreSQL to start - 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
Pinned Solution
a month ago
Try setting the custom start command to sleep infinity and redeploy.
5 Replies
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
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.
a month ago
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.
a month ago
I cannot access the Console because the service crashes immediately on startup before I can connect. Could you please either:
- Run
pg_resetwal /var/lib/postgresql/dataon your side, or - 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.
a month ago
Try setting the custom start command to sleep infinity and redeploy.
0x5b62656e5d
Try setting the custom start command to `sleep infinity` and redeploy.
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
