PostgreSQL: Documentation: 7.1: Multi-Version Concurrency Control
Multi-Version Concurrency Control (MVCC) is an advanced technique for improving database performance in a multi-user environment. Vadim Mikheev ( ) provided the implementation for Postgres.
PostgreSQL: Documentation: 7.1: Multi-Version Concurrency Control July 16, 2026: PostgreSQL 19 Beta 2 Released! Documentation → PostgreSQL 7.1 Supported Versions: Current ( 18 ) / 17 / 16 / 15 / 14 Development Versions: 19 / devel Unsupported versions: 13 / 12 / 11 / 10 / 9.6 / 9.5 / 9.4 / 9.3 / 9.2 / 9.1 / 9.0 / 8.4 / 8.3 / 8.2 / 8.1 / 8.0 / 7.4 / 7.3 / 7.2 / 7.1 This documentation is for an unsupported version of PostgreSQL. You may want to view the same page for the current version, or one of the other supported versions listed above instead. PostgreSQL 7.1.3 Documentation Prev Next Ch
related reading
- Multiversion concurrency control - Wikipediaen.wikipedia.org
- GitHub - jorzel/concurrency-control: In this repo I would like to show 4 strategies of concurrency control for writing data using Python SQLAlchemy ORM and PostgresSQL (however this examples could be easily transformed to plain SQL).github.com
- DBMS Musings: It’s Time to Move on from Two Phase Commitdbmsmusings.blogspot.com
- PostgreSQL rocks, except when it blocks: Understanding locks - Citus Datacitusdata.com
- Snapshot isolation - Wikipediaen.wikipedia.org
- PostgreSQL: Documentation: 18: 13.2. Transaction Isolationpostgresql.org
- An Overview of Distributed PostgreSQL... | Crunchy Data Blogcrunchydata.com
- Explaining The Postgres Memeavestura.dev
- 67.4. Two-Phase Transactionspostgresql.org
- Schedule | POSETTE: An Event for Postgres 2024 - Citus Datacitusdata.com
- Databases in 2025: A Year in Review // Blog // Andy Pavlo - Carnegie Mellon Universitycs.cmu.edu
- Three-phase commit protocolen.wikipedia.org