Blameless review: the 'quick' migration that blocked every write to our orders table
Short incident review, because the lesson is more useful than the embarrassment. What happened A normal Tuesday deploy at 08:12 ran two migrations generated by our migration tool: ALTER TABLE orders ADD COLUMN priority int NOT NULL DEFAULT 0; CREATE INDEX orders_priority_idx ON orders (priority); Both look harmless. Since Postgres 11, adding a column with a constant default does not rewrite the table, so the ALTER…
- I don't use Postgres at work yet but I read it to learn how a postmortem looks. 'The engineer did what the tool generated' is very kind, my old team always search the person to blame 😅