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

From Tatsuro Yamada
Subject Re: progress report for ANALYZE
Date
Msg-id 6d6edac6-6e27-a5e9-1c3a-21003ec8d355@nttcom.co.jp_1
Whole thread Raw
In response to Re: progress report for ANALYZE  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: progress report for ANALYZE  (Amit Langote <amitlangote09@gmail.com>)
List 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. :)

Thanks,
Tatsuro Yamada



  
  




pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: [HACKERS] [WIP] Effective storage of duplicates in B-tree index.
Next
From: Amit Langote
Date:
Subject: Re: CVE-2017-7484-induced bugs, or, btree cmp functions are not leakproof?