Break production. Undo it. Postgres with transaction-level undo. Reverse one bad transaction, not the whole database. Your database production purchase_orders live Undo any write Reverse an UPDATE , a DELETE , or a whole bad batch after it commits. Built for agents One command per recovery. --json and stable exit codes on every one. Surgical Only the rows the transaction touched. Every other write stays put. Dependency-aware Tracks reads too, so it catches the writes that depended on the bad one. Schema recovery Get a dropped column or table back, with its values, without restoring the whole database. Time travel Read a table as it was at any past moment. Revert a whole window in one command. Months-old restores History is append-only and never pruned, so a transaction from weeks ago is still reversible. PostgreSQL 18 Your drivers, your SQL, your extensions. Undo a DELETE . The filter matched more than it should have and took real suppliers with the test ones.…