The companion blog post from TigerBeetle is great too--dives into detail on the bug we found in the index-intersection query code:
https://tigerbeetle.com/blog/2025-06-06-fuzzer-blind-spots-meet-jepsen/

Justin Jaffray has written up a lovely companion to this piece, diving into Snapshot Isolation and how to understand transaction dependency structures. https://buttondown.com/jaffray/archive/how-to-understand-that-jepsen-report/

Thanks to AWS's Sergey Melnik, as well as HN commenters matashii and Ants Aasma, we now know that Long Fork in PostgreSQL clusters is caused by a disagreement between primaries and secondaries on the order in which transactions become visible […]

For the daytime crew: Jepsen's distributed systems class starts next week. The accompanying workshop, where we practice writing and debugging our own distributed systems, follows the week after […]

Woke up to a bunch of excellent emails--y'all rock. Will try to write back to everyone in the next hour or so. ❤️

Thanks to everyone who wrote in objecting to the report's description of data loss due to auto-commit. Some experiments this morning suggest that we got it wrong (at least for the official Java client). We've published an update to the report: https://jepsen.io/analyses/bufstream-0.1.0#updates