Replay · Scope blow-up
An agent changed one row and a trigger changed 301
The same pattern, retold on a small store database with fictional data. No names or data from any real incident.
The request
A support agent is asked to mark order 42 as shipped.
What ran
UPDATE orders SET status = 'shipped' WHERE id = 42What the agent said
Done, 1 row.
What Postgres committed
Postgres committed 301 rows in public.orders: a legacy trigger on the table rewrote 300 more orders in the same transaction.
The check
Doesn’t match
The undo preview
The undo preview lists all 301 rows with their values before the update, and runs only after a person approves it.