Re: [HACKERS] ANALYZE command progress checker - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] ANALYZE command progress checker
Date
Msg-id 9aeb9b53-1f51-6bf8-1465-ed73f4ef0ee1@2ndquadrant.com
Whole thread Raw
In response to [HACKERS] ANALYZE command progress checker  (vinayak <Pokale_Vinayak_q3@lab.ntt.co.jp>)
Responses Re: [HACKERS] ANALYZE command progress checker  (David Fetter <david@fetter.org>)
List pgsql-hackers
On 2/28/17 04:24, vinayak wrote:
> The view provides the information of analyze command progress details as 
> follows
> postgres=# \d pg_stat_progress_analyze
>            View "pg_catalog.pg_stat_progress_analyze"

Hmm, do we want a separate "progress" system view for every kind of
command?  What if someone comes up with a progress checker for CREATE
INDEX, REINDEX, CLUSTER, etc.?

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] log_autovacuum_min_duration doesn't log VACUUMs
Next
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] objsubid vs subobjid