ORCIDGitHubLinkedIn
RSS Curriculum Vitae TR

Write Skew

Turkish equivalent: Yazma sapmasıDomain: Databases

A concurrency anomaly in snapshot-style isolation where transactions update different rows after reading a shared predicate and jointly violate an invariant.

Database Context

Write skew can occur under snapshot-style isolation when two transactions read a shared predicate, then update different rows and jointly violate an invariant. For example, two on-call records can each be disabled after both transactions observe that another active record still exists.

Isolation Boundary

Write skew is not a lost update: the transactions usually write different rows, so no direct write-write conflict exposes the invariant violation.

Updated:

Related concepts

Databases

Related technical publications

Publications whose title or summary directly references this concept.

Concurrency in Distributed Data Systems

Concurrency in distributed data systems depends on the interaction of MVCC, isolation levels, lost updates, write skew, and replication visibility rather than on a single database setting.