Has a SQL migration ever taken down your production database? How did you handle it?
I'm a backend engineer building a tool to prevent Postgres migration outages and I'm in pure research mode right now — no product pitch, just trying to understand how widespread this is.
Our worst case: an ALTER TABLE on a 30M row table held an AccessExclusiveLock for 22 minutes. Everything queued up. Users saw timeouts. We found out from customer support, not monitoring.
Has this happened to your team? How do you currently check migrations before pushing to prod? Do you use squawk, strong_migrations, manual review, or just hope for the best?
Genuinely trying to understand the problem before I build anything. All experiences welcome.
u/Gadimov03 — 6 days ago