| From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Tatsuro Yamada <tatsuro(dot)yamada(dot)tf(at)nttcom(dot)co(dot)jp>, vignesh C <vignesh21(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: progress report for ANALYZE |
| Date: | 2019-11-27 02:34:26 |
| Message-ID: | CA+HiwqH_CxrSLwrNP=gWbbZUN9aQuv4+9qGgEPmacPWyLfmwiQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Nov 26, 2019 at 9:22 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Artur Zakirov | 2019-11-27 02:35:14 | Re: pg_upgrade fails with non-standard ACL |
| Previous Message | Amit Kapila | 2019-11-27 02:22:49 | Re: SegFault on 9.6.14 |