PostgreSQL DB crashed
Anonymous
PROOP

17 days ago

Agent created a new DB. But then all the credits are messed up. It's not connecting to the new DB. I'm getting issues. I don't know what happened, but I don't think it's an issue from our end as of now. So, if you can, just do some recovery and get that state back to like 20th May.

$20 Bounty

2 Replies

Railway
BOT

17 days ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open Railway 17 days ago


Can you provide the deployment logs for the service?


15 days ago

if the agent created a new DB, your app is probably connected to that new empty DB now, not the old one.

I would first find the original Postgres service/volume and copy its DATABASE_URL somewhere safe. then compare it with what your app has now. if they differ, point the app back to the original DB service and redeploy.

getting the exact May 20 state only works if you have a backup/PITR/snapshot from then. if not, safest path is recover from the old volume, dump it, and restore into a clean new Postgres.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...