Re: Improvements and additions to COPY progress reporting

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(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-02-25 08:14:35
Message-ID: YDdcayzvkIDm2mwI@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 24, 2021 at 01:53:03AM -0600, Justin Pryzby wrote:
> On Sun, Feb 21, 2021 at 08:10:09PM +0100, Matthias van de Meent wrote:
> I think these should say that they report their progress *in* the view (not
> "to"):
>
> > + Each backend running <command>ANALYZE</command> will report its progress to
> > + the <structname>pg_stat_progress_analyze</structname> view. See

What is proposed in the patch is:
"Each backend running <command>blah</> will report its progress to the
pg_stat_progress_blah view."

What you propose is:
"Each backend running <command>blah</> will report its progress in the
pg_stat_progress_blah view."

What pg_basebackup tells is:
"Whenever <application>pg_basebackup</application> is taking a base
backup, the server's pg_stat_progress_basebackup view will report the
progress of the backup."

Here is an extra idea:
"Whenever a backend runs <command>blah</>, the server's
pg_stat_progress_blah will report the progress of this command."
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dmitry Dolgov 2021-02-25 08:22:43 Re: Asynchronous and "direct" IO support for PostgreSQL.
Previous Message Michael Paquier 2021-02-25 08:05:27 Re: doc review for v14