Show HN: EterDB, a Postgres fork that makes it easy to recover from incidents

2 comments

• micw 1 hour ago
  The idea looks interesting. But when I think of "make incident recovery easy", the very last thing I want is a fork that differs from the standard that everyone else is running. I would have a better feeling if that would be an extension, not a fork.
  [-]
  • maxloh 8 minutes ago
    From the README,

      It is PostgreSQL 18. One piece, read-dependency capture, has to be in the engine, and it ships as a small upstream-tracked patch. Extensions including pgvector, your ORM, and your SQL dialect all work unchanged.
    

    https://github.com/eterdb/eterdb#how-it-works
• NewJazz 3 days ago
  Uh, pitr is a thing in many many postgresql management layers.

  https://pgbarman.org/

  [-]
  • fdeth 2 days ago
    Yes, but PITR is not surgical, you can’t easily undo just the faulty transactions.