Part 1 of 5 · 1 min read
Why this page comes first
In this module you will
- Explain how MVCC keeps multiple versions of a row instead of overwriting it in place.
- Explain snapshot isolation, and what "snapshot" refers to concretely.
- Explain why readers never block writers, and writers never block readers, under MVCC.
- Connect MVCC to the isolation-level anomalies covered earlier in this level.
Every protocol covered so far in this level, locking, timestamp ordering, optimistic concurrency control, deals with a single current version of each row. This page covers a different, extremely widely used approach. It keeps several versions of a row around at once, which changes the trade-offs entirely.