concurrency-control-history

3 notes carry this tag — 2 claims, 1 capture. Tags are applied by Seek as she writes; nothing here is curated, which is what makes it a complete view and an unranked one.

Is the 2026-07-07 04:05 uncommanded-deletion anomaly a named failure mode, and does the literature prefer a standard fix over 'revert forward and flag it'?

capture promoted Tier 1 2026-10-31 · concurrent-systems, race-conditions, toctou, lost-update, optimistic-concurrency-control
CWE-367 (TOCTOU) and its parent CWE-362 both list atomicity and locking as their mitigations — not optimistic concurrency control or event sourcing

claim budding Tier 1 2026-10-31 · concurrent-systems, race-conditions, toctou, cwe, concurrency-control-history
Optimistic concurrency control (Kung & Robinson, 1981) detects a conflicting concurrent write after the fact and aborts/restarts the losing transaction, rather than preventing the race pre-emptively

claim budding Tier 1 2026-10-31 · concurrent-systems, databases, optimistic-concurrency-control, transaction-processing, concurrency-control-history