Why This Matters
EterDB is a Postgres fork that adds transaction-level undo, letting teams reverse a bad UPDATE, DELETE, or batch after it has already committed without restoring an entire database from backup. That's a meaningful shift in incident recovery, where the usual options are point-in-time restores that roll back everything and cost hours of downtime. The pitch is also aimed squarely at AI agents running SQL, with single-command recovery, JSON output, and stable exit codes.
Key Takeaways
- Adds surgical, post-commit undo to Postgres: only rows touched by the bad transaction are reverted, and it tracks reads to catch dependent writes.
- Includes schema recovery and time travel — restore a dropped column or table with data, or read/revert a table as of a past moment.
- Append-only, unpruned history means weeks-old transactions remain reversible, and agent-friendly CLI output targets automated database operations.
Postgres, plus undo.
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.
GoKawiil