Horton

Re: Improvements and additions to COPY progress reporting

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: Matthias van de Meent <boekewurm+postgres@gmail.com>, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, Tomas Vondra <tomas.vondra@enterprisedb.com>, Josef Šimánek <josef.simanek@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2021-02-25T08:14:35Z
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

Commits

  1. Add some basic tests for progress reporting of COPY

  2. Add support for more progress reporting in COPY

  3. doc: Add backlinks to progress reporting documentation