News for hackers. Stuff that matters.
Re:Postgres transactions are a distributed systems superpower by mrkeen on Friday July 03, 2026 @05:27AM (#48772901)
I have the starting state:

  DB={}    Q={}
I would like to either remain in the starting state, or enter a new state:

  DB={Bob paid $15}  Q={Bob paid $15}
But this is Two Generals, which is impossible.

If you invoke 2PC, you want the states to progress thus:

  DB={locked}        Q={locked}

  DB={locked;        Q={locked;
      Bob paid $15}     Bob paid $15}

  DB={locked;        Q={locked;
      Bob paid $15;     Bob paid $15;
      unlocked}         unlocked}
A strictly harder problem, right?
Re:Postgres transactions are a distributed systems superpower by dcminter on Friday July 03, 2026 @09:11AM (#48774607)
Ah, you're assuming distributed, which I wasn't. We are not at home to partition tolerance :)

Makes sense in the context of the original post though.

Re:Postgres transactions are a distributed systems superpower by pragmatic on Friday July 03, 2026 @10:08AM (#48775277)
But you are assuming distributed transactions as soon as you have two systems participating in the transaction.

It's a recipe for deadlocks and even live locks.

That's a reason industry moved away from this. Bc when it works it's magic. But when the problems start it's pure hell.