On 2019-05-27 20:18, 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 reasona
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
On Mon, May 27, 2019 at 11:20:28AM -0700, Andres Freund wrote:
> 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
On Mon, May 27, 2019 at 4:51 PM Alvaro Herrera
wrote:
>
> On 2019-May-27, 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 i
On 2019-May-27, 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
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
