Have I killed one of your servers? :(
Howdy. Not sure if Railway does this, but some hosts share database instances among customers. (Pretty sure PythonAnywhere account does, for example.) I run a Postgres instance and have somehow, during an Alembic upgrade, killed it: all queries are timing out. If this affects other customers, please check out deployment ID 9bb45cb4-352a-4502-babb-89c73cb312ad and kill it with as much fire as you need.
Otherwise, I'll solve it.
I have never done this kind of damage to a database before :/ First time using Alembic too.
Solution:Jump to solution
thank you for thinking about other users, but I'm happy to say that we don't share databases across multiple customers, each user who deploys any database gets their own database that only they can use.
3 Replies
Project ID:
9bb45cb4-352a-4502-babb-89c73cb312adUpdate: a dozen locks, 240 blocked transactions
Solved, aka, all transactions killed. Hopefully this was isolated and did not affect anyone else running instances on the same machine or anything.
Solution
thank you for thinking about other users, but I'm happy to say that we don't share databases across multiple customers, each user who deploys any database gets their own database that only they can use.