Re: Improvements and additions to COPY progress reporting

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Josef Šimánek <josef(dot)simanek(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Improvements and additions to COPY progress reporting
Date: 2021-03-04 10:38:08
Message-ID: YEC4kHMGaJIR6PZB@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 04, 2021 at 12:16:17PM +0530, Bharath Rupireddy wrote:
> IMO, the phrasing proposed by Justin upthread looks good. It's like this:
>
> > + Each backend running <command>ANALYZE</command> will report its progress in
> > + the <structname>pg_stat_progress_analyze</structname> view. See

No objections to just go with that. As a new patch set is needed, I
am switching the CF entry to "Waiting on Author".
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2021-03-04 10:52:57 Re: [HACKERS] logical decoding of two-phase transactions
Previous Message Dilip Kumar 2021-03-04 10:33:26 Re: [HACKERS] Custom compression methods