New comment by forgotmy_login in "The startup's Postgres survival guide"

forgotmy_login — Wed, 22 Jul 2026 16:29:44 +0000

Recalling from my previous studies here: I think you can use Serializable Isolation Level, the strictest level - this will cause one of the two to fail (that is; fail only when the two txns affected rows that would logically conflict). And then you build the expectation of such possible transaction failures into the code and treat retries as a first-class expectation. Does this get to what you're trying to solve at all?

Hacker News: forgotmy_login

New comment by forgotmy_login in "The startup's Postgres survival guide"