Reposted by Klaus Aschenbrenner
PostgreSQL MVCC is often criticized for storing old versions in place. But the question is: does it have to traverse a chain of versions to find the correct row? A new blog post to answer that: dev.to/franckpachot...
dev.to
PostgreSQL MVCC: Why Bloat Doesn't Automatically Mean Expensive Reads
One of the most persistent misconceptions about PostgreSQL MVCC is that old row versions accumulate...