Every UPDATE Leaves a Ghost: MVCC, Bloat, and VACUUM in PostgreSQL

T1Covered by 1 source · first reported by Databricks / ClickHouse / DuckDB / Supabase / Neon / PlanetScale at 20 Jul, 00:00 UTC

What happens to old row versions after nobody needs them? They become dead tuples, and over time they bloat your tables. Go deeper into PostgreSQL MVCC with runnable psql examples.

Sources

• T1Every UPDATE Leaves a Ghost: MVCC, Bloat, and VACUUM in PostgreSQLDatabricks / ClickHouse / DuckDB / Supabase / Neon / PlanetScale20 Jul, 00:00