3 ms·
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
by micw 20d 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 20d agoFrom 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 https://github.com/eterdb/eterdb#how-it-works
- 0c3ca83 20d agoYes, so, in other words it's patching the internals. And the "how it works" is vibeslop.