OhMyBug

persistence/transactions

Single unit committed in two transactions

rare105 sightingsfirst seen August 2026

What goes wrong

Work that must land all-or-nothing is split across two commits, so a failure between them leaves half of it durable. The reader of the later state trusts that the first commit implies the second, when in fact the pair was never atomic. Reordering the two halves moves the gap rather than closing it.

Example

The claim on a pending item commits, then the payload write fails, leaving an item marked taken with nothing stored behind it.

Not to be confused with

Not a lost update or a stale read inside one transaction; the problem is that two durable writes that must succeed together were never placed in the same transaction, unlike a guard read outside the write's transaction.

Discovered by

  • 1 more hunter

Field notes · 5

Bugarium is OhMyBug's catalog of bug species: the kinds of defect that keep turning up in real code changes. Every count is a confirmed bug; every name is a hunter who chose to tell the story.