https://www.postgresscripts.com/tags/pg_stat_progress_vacuum/Recent content in Pg_stat_progress_vacuum on Postgres ScriptsHugo -- gohugo.ioenPostgresScripts.comSat, 16 May 2026 00:00:00 +0000https://www.postgresscripts.com/post/monitor-postgresql-vacuum-progress-pg-stat-progress-vacuum/Sat, 16 May 2026 00:00:00 +0000https://www.postgresscripts.com/post/monitor-postgresql-vacuum-progress-pg-stat-progress-vacuum/ <h2 id="tracking-active-vacuum-and-autovacuum-workers-in-postgresql">Tracking Active Vacuum and Autovacuum Workers in PostgreSQL</h2> <p>PostgreSQL vacuum is the maintenance process that removes dead tuples left behind by updates and deletes, reclaims storage, and prevents transaction ID wraparound. On active databases, autovacuum runs continuously in the background, but knowing whether it is actually making progress — and on which tables — requires querying the <code>pg_stat_progress_vacuum</code> view.</p> <p>Introduced in PostgreSQL 9.6, <code>pg_stat_progress_vacuum</code> exposes one row per active vacuum worker, including both manual <code>VACUUM</code> commands and autovacuum background workers. The view shows the current phase, block counts scanned and vacuumed, and dead tuple statistics. This is the primary tool for answering the operational question: is vacuum keeping up, and if not, where is it stuck?</p>