Deep technical analysis of PostgreSQL's MVCC implementation and how different databases (Oracle, MySQL, SQL Server, MongoDB) make different trade-off choices. Explores the design decisions behind common database architectures.
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.
About this link
- Saved
- Last checked
- Not checked yet
- Metadata retrieved
- Not recorded