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.
Summary
PostgreSQL’s multi-version concurrency control (MVCC) has its flaws, leading to table bloat and increased write operations. The article compares how various database systems, including Oracle and SQL Server, tackle similar design challenges, revealing trade-offs that come with each approach.
Comments (6 of ) ⌛