News for hackers. Stuff that matters.
Re:Jepsen: MongoDB 4.2.6 by politician on Sunday May 24, 2020 @03:18PM (#23293893)
Jepsen reports often include two distinct types of analyses: correctness in a distributed storage system under a variety of failure scenarios, and in-depth analysis of consistency claims. Both examinations are extremely helpful.

In a single write master configuration, Postgres runs transactions concurrently, so the consistency analysis is still quite relevant.

I don’t think it’s a stretch to say that everyone expects Postgres to get top marks in this configuration and it would be worth confirming that this is the case.

Re:Jepsen: MongoDB 4.2.6 by takeda on Sunday May 24, 2020 @03:42PM (#23294087)
Actually he already did analyze PostgreSQL: https://aphyr.com/posts/282-call-me-maybe-postgres

But it was long ago, and maybe needs to be redone?

Edit: after re-reading it he treats it as a distributed system because client and server is over network. And that is true, it can also be thought of as a distributed system because as you said transactions are concurrent and are running as separate processes. Although in these cases you can't have a partition (which aphyr uses to find weaknesses), or maybe there is something equivalent that happens?