Accidental TRUNCATE on production Postgres — any snapshot recoverable?
amanuelt312
HOBBYOP

a month ago

Account: amanuelt312@gmail.com

Project: new path — environment production — service Postgres

Volume: postgres-volume (intact, Status: Ready, 223MB/5000MB)

A script accidentally ran TRUNCATE ... CASCADE against my production database today (2026-07-15) between approximately 18:28 and 18:35 local time, emptying every table in the public schema. Only _prisma_migrations survived.

I did not have backups or PITR enabled (I'm not on Pro), so I have nothing to restore from. The volume itself has never been wiped, deleted, or recreated.

My question: does any infrastructure-level snapshot of this volume exist from before 18:28 today that could be recovered? I understand this is unlikely without backups enabled — I just want to confirm before I write the data off.

I've stopped writes to the database in the meantime. Any guidance appreciated.

Thanks,

Amanuel

Solved

1 Replies

Railway
BOT

a month ago

We don't recover data lost to user-initiated actions such as an accidental TRUNCATE, and our databases are unmanaged, so automatic snapshots, WAL recovery, and PITR aren't available to recover your data unless you had set up volume backups or PITR yourself beforehand. Going forward, you can enable volume backups on your Postgres service from its Settings page so you can self-restore if something like this happens again.


Status changed to Awaiting User Response Railway about 1 month ago


Railway
BOT

a month ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 30 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...