Re: ANALYZE command progress checker

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: vinayak <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ANALYZE command progress checker
Date: 2017-03-01 14:45:40
Message-ID: 9aeb9b53-1f51-6bf8-1465-ed73f4ef0ee1@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2017-03-01 14:51:36 Re: objsubid vs subobjid
Previous Message Peter Eisentraut 2017-03-01 14:43:31 Re: log_autovacuum_min_duration doesn't log VACUUMs