PostgreSQL's MVCC: Trade-Offs Across Database Engines

PostgreSQL's MVCC is bad. So is everyone else's.

The critics are right: PostgreSQL's MVCC bloats tables and amplifies writes. Oracle, InnoDB, SQL Server, MongoDB, LSM stores, and etcd answer the same four design questions differently, and each pays for it somewhere else.

boringsql.com

PostgreSQL's MVCC: Trade-Offs Across Database Engines

PostgreSQL's MVCC is bad. So is everyone else's.

Discussion

Library

PostgreSQL's MVCC: Trade-Offs Across Database Engines

PostgreSQL's MVCC is bad. So is everyone else's.