Re: Add command column to pg_stat_progress_create_index

From: David Fetter <david(at)fetter(dot)org>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add command column to pg_stat_progress_create_index
Date: 2019-05-28 12:40:27
Message-ID: 20190528124027.GF12249@fetter.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, May 27, 2019 at 11:20:28AM -0700, Andres Freund wrote:
> Hi,
>
> On 2019-05-27 14:18:12 -0400, Peter Eisentraut wrote:
> > I propose to add a column "command" to pg_stat_progress_create_index.
> > The sibling view pg_stat_progress_cluster already contains such a
> > column. This can help distinguish which command is running and thus
> > which phases to expect. It seems reasonable to keep these views
> > consistent, too. (They are both new in PG12.) Patch attached.
>
> Seems like we should do that for v12 then?

+1

Best,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message RAJIN RAJ K 2019-05-28 14:36:16 Alternate methods for multiple rows input/output to a function.
Previous Message Andres Freund 2019-05-28 11:45:24 Re: Remove page-read callback from XLogReaderState.