Multiple ChoiceBeginner 45s
Postgres autovacuum bloat cause
Why does a Postgres table experience bloat over time under heavy update load?
Options
- 1Updates overwrite rows in place, which corrupts pages and forces a full rebuild before reuse
- 2Indexes store duplicated copies of columns by design, so space growth is inherent to indexes
- 3The WAL permanently doubles every row's size, so space grows forever and is never reclaimed by maintenance
- 4Updates create new row versions (MVCC); dead tuples persist until vacuum reclaims them
Think you can answer under pressure?
Get matched and answer live questions in 3-minute 1v1 battles. Elo ranking, badge tiers and bragging rights on the line.