Re: progress report for ANALYZE - Mailing list pgsql-hackers

From Amit Langote
Subject Re: progress report for ANALYZE
Date
Msg-id CA+HiwqH_CxrSLwrNP=gWbbZUN9aQuv4+9qGgEPmacPWyLfmwiQ@mail.gmail.com
Whole thread Raw
In response to Re: progress report for ANALYZE  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List 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



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: SegFault on 9.6.14
Next
From: Artur Zakirov
Date:
Subject: Re: pg_upgrade fails with non-standard ACL