https://www.postgresscripts.com/tags/progress-reporting/Recent content in Progress Reporting on Postgres ScriptsHugo -- gohugo.ioenPostgresScripts.comThu, 18 Jun 2026 00:00:00 +0000https://www.postgresscripts.com/post/monitor-postgresql-analyze-progress-with-pg-stat-progress-analyze/Thu, 18 Jun 2026 00:00:00 +0000https://www.postgresscripts.com/post/monitor-postgresql-analyze-progress-with-pg-stat-progress-analyze/ <h2 id="monitor-postgresql-analyze-progress-with-pg_stat_progress_analyze">Monitor PostgreSQL ANALYZE Progress with pg_stat_progress_analyze</h2> <p>Running <code>ANALYZE</code> on a multi-hundred-gigabyte table and wondering whether it is halfway done or barely started is a common operational question with, until recently, no good answer. <code>pg_stat_progress_analyze</code> answers it: a live view that reports the current phase of every running ANALYZE and how many sample blocks it has scanned.</p> <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1012089347386563" crossorigin="anonymous"></script> <ins class="adsbygoogle" style="display:block" data-ad-client="ca-pub-1012089347386563" data-ad-slot="7945792173" data-ad-format="auto" data-full-width-responsive="true"></ins> <script> (adsbygoogle = window.adsbygoogle || []).push({}); </script> <h2 id="purpose-and-overview">Purpose and Overview</h2> <p><code>ANALYZE</code> collects column statistics that the query planner depends on to choose good plans. On a small table it finishes in milliseconds and nobody thinks about it. On a very large table, or one with many child partitions, it can run for minutes, and during that window two questions matter: is it actually making progress, and how long until it is done. A manual <code>ANALYZE</code> issued before a big read-heavy job, or an autovacuum-launched analyze competing for I/O, both raise the same need for visibility.</p>