GoKawiilEterDB launches as a Postgres fork with built-in undo for database writes
A new open-source project called EterDB extends PostgreSQL with the ability to reverse individual transactions, including updates, deletes, or entire batches, even after they have been committed. It tracks dependencies between reads and writes so that changes relying on a bad transaction are also caught, and it retains an append-only history that allows recovery of data from weeks or months earlier.
GoKawiil's interpretation of the reporting above, not reported fact.
Database incidents like accidental deletes or bad migrations traditionally require full backups or point-in-time restores that affect the entire dataset, causing downtime and data loss for unrelated records. EterDB's surgical, transaction-level undo could let engineering teams fix mistakes in seconds without disrupting other data, which is especially valuable for automated agents or scripts that might make erroneous writes.
- EterDB is a Postgres fork designed to undo specific transactions rather than requiring full database restores.
- It tracks read dependencies to prevent inconsistent states after a rollback, and supports schema-level recovery.
- Its append-only history enables time travel and reversal of changes from far in the past, aimed at automated recovery workflows.
Source: eterdb.com, 2026-09-10
Published there as: “Show HN: EterDB, a Postgres fork that makes it easy to recover from incidents”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.