Re: Improvements and additions to COPY progress reporting
Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
From: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Justin Pryzby <pryzby@telsasoft.com>, Matthias van de Meent <boekewurm+postgres@gmail.com>, Tomas Vondra <tomas.vondra@enterprisedb.com>, Josef Šimánek <josef.simanek@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2021-03-04T06:46:17Z
Lists: pgsql-hackers
On Thu, Feb 25, 2021 at 1:44 PM Michael Paquier <michael@paquier.xyz> wrote: > > 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." 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 > + Each backend running <command>CREATE INDEX</command> will report its > + progress in the <structname>pg_stat_progress_create_index</structname> view ... ... With Regards, Bharath Rupireddy. EnterpriseDB: http://www.enterprisedb.com
Commits
-
Add some basic tests for progress reporting of COPY
- 15639d5e8f6f 14.0 landed
-
Add support for more progress reporting in COPY
- 9d2d45700928 14.0 landed
-
doc: Add backlinks to progress reporting documentation
- 8a8f4d8ede28 14.0 landed