Re: progress report for ANALYZE

From: Tatsuro Yamada <tatsuro(dot)yamada(dot)tf(at)nttcom(dot)co(dot)jp>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Amit Langote <amitlangote09(at)gmail(dot)com>, 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:01:37
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Hi Alvaro!

On 2019/11/26 21:22, Alvaro Herrera 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.

Thanks for your comment!
Okay, I'll add the column "ext_stats_total" to
pg_stat_progress_analyze view on the next patch. :)

Regarding to other total number columns,
I'll create another patch to add these columns "index_vacuum_total" and
"index_rebuild_count" on the other views. :)

Tatsuro Yamada

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2019-11-27 02:03:34 Re: CVE-2017-7484-induced bugs, or, btree cmp functions are not leakproof?
Previous Message Peter Geoghegan 2019-11-27 01:28:50 Re: [HACKERS] [WIP] Effective storage of duplicates in B-tree index.