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: Matthias van de Meent <boekewurm+postgres@gmail.com>
Cc: 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>, Justin Pryzby <pryzby@telsasoft.com>
Date: 2021-02-24T07:46:57Z
Lists: pgsql-hackers 
On Tue, Feb 23, 2021 at 10:27:24AM +0100, Matthias van de Meent wrote:
> Note, I'm happy to be proven wrong here, in which case I don't
> disagree, but according to my limited knowledge, these outputs should
> be stable.

I am planning to look more at 0001 and 0003, but for now I have been
looking at 0002 which is interesting on its own.

+    <structname>pg_stat_progress_vacuum</structname> view. Backends running
+    <command>VACUUM</command> with the <literal>FULL</literal> option report
+    progress in the <structname>pg_stat_progress_cluster</structname> instead.
You have missed one "view" after pg_stat_progress_cluster here.
Except that, this stuff looks fine.  So I'd like to apply it if there
are no objections.
--
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