Comment

Comment by forgotmy_login

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?

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton