Why Database Snapshot Isolation Breaks at Write Skew
from Database Tech with Fexingo: SQL, NoSQL, and Data Storage Conversations Hosted by Fexingo
Episode 116 of Database Tech with Fexingo. Lucas and Luna dive into write skew, a subtle concurrency anomaly that breaks snapshot isolation even when individual transactions are consistent. Using the classic doctor-on-call scheduling example, they explain how PostgreSQL's default snapshot isolation can allow two overlapping transactions to violate a business rule without ever reading each other's data. They contrast this with serializable isolation, which uses predicate locks and serialization anomalies to catch write skew, and discuss real-world tradeoffs: performance cost versus correctness. If you've ever assumed MVCC means no conflicts, this episode will change your mind. Perfect for engineers using PostgreSQL, MySQL (with InnoDB), or any database relying on snapshot isolation. Includes concrete steps to test for write skew and when to escalate isolation levels. #WriteSkew #SnapshotIsolation #PostgreSQL #MVCC #ConcurrencyControl #DatabaseAnomalies #SerializableIsolation #PredicateLocks #DoctorOnCall #BusinessLogic #TransactionIsolation #SQL #NoSQL #DatabasePerformance #FexingoBusiness #TechnologyPodcast #DatabaseEngineering #Episode116 Keep every episode free: buymeacoffee.com/fexingo
Embed this episode
No transcript yet.