Re: progress report for ANALYZE
Amit Langote <amitlangote09@gmail.com>
From: Amit Langote <amitlangote09@gmail.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Tatsuro Yamada <tatsuro.yamada.tf@nttcom.co.jp>,
vignesh C <vignesh21@gmail.com>, Pg Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-11-27T02:34:26Z
Lists: pgsql-hackers
On Tue, Nov 26, 2019 at 9:22 PM Alvaro Herrera <alvherre@2ndquadrant.com> wrote: > > On 2019-Nov-26, Tatsuro Yamada wrote: > > > > I wonder whether we need the total number of ext stats on > > > pg_stat_progress_analyze or not. As you might know, there is the same > > > counter on pg_stat_progress_vacuum and pg_stat_progress_cluster. > > > For example, index_vacuum_count and index_rebuild_count. > > > > Would it be better to add the total number column to these views? :) > > Yeah, I think it would be good to add that. Hmm, does it take that long to calculate ext stats on one column? The reason it's worthwhile to have index_vacuum_count, index_rebuild_count, etc. is because it can take very long for one index to get vacuumed/rebuilt. Thanks, Amit
Commits
-
Doc: Fix and tweak documentation for ANALYZE reporting
- 5ba40b62318e 13.0 landed