Blog

Your dream job? Lets Git IT.
Interactive technical interview preparation platform designed for modern developers.

XGitHub

Platform

  • Categories

Resources

  • Blog
  • About the app
  • FAQ
  • Feedback

Legal

  • Privacy Policy
  • Terms of Service

© 2025 LetsGit.IT. All rights reserved.

LetsGit.IT/Categories/PostgreSQL
PostgreSQLhard

PostgreSQL bloat: what causes it and how do you reduce it?

Tags
#postgres#mvcc#vacuum#bloat#performance
Back to categoryPractice quiz

Answer

Because of MVCC, updates/deletes create dead tuples that must be cleaned up by VACUUM. Bloat happens when cleanup can’t keep up (heavy updates, long transactions, poor autovacuum settings), so tables/indexes grow. Mitigation: tune autovacuum, avoid long transactions, and periodically `REINDEX`/`VACUUM (FULL)` or use online tools like pg_repack when needed.

Related questions

PostgreSQL
How do `pg_stat_activity` and `pg_stat_statements` help in troubleshooting?
#postgres#monitoring#pg_stat_activity
PostgreSQL
Materialized view vs view: what’s the difference?
#postgres#views#materialized-view
PostgreSQL
LISTEN/NOTIFY: what problem does it solve?
#postgres#listen-notify#pubsub
PostgreSQL
Advisory locks: what are they and when would you use them?
#postgres#locks#advisory
PostgreSQL
BRIN index: when is it useful?
#postgres#brin#indexes
PostgreSQL
GIN vs GiST indexes: when would you use each?
#postgres#indexes#gin