I've had the same today. I redeployed postgres instead of restarting it and it came back online

I also redeployed but Migrating data from local instance is not working

that migration error usually means the source DB is still dying while Django is reading from it, not that your local migration command is wrong.

I would avoid running Django migrations as the recovery method. first get a dump from the old DB with pg_dump, then restore that into a fresh empty Postgres with psql/pg_restore.

if the old DB only stays up briefly, run the dump from a temporary Railway service in the same project/network so latency is low. after restore, point Django to the new DB and only then run migrations if the schema actually needs it.

Thank you. I wish I had this information before deleting the database. It was just a test website for I didn’t loose any data.

yeah hahaha. lost a bit too many nights with similar mistakes too