MVCC and Transactions

Postgres never updates a row in place — it writes a new version and leaves the old one for vacuum to reclaim. That one design choice explains isolation levels, dead tuples, bloat, autovacuum tuning, and transaction ID wraparound, all common senior-level questions.