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: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Cc: Tomas Vondra <tomas.vondra@enterprisedb.com>, Matthias van de Meent <boekewurm+postgres@gmail.com>, Josef Šimánek <josef.simanek@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Justin Pryzby <pryzby@telsasoft.com>
Date: 2021-02-20T23:23:02Z
Lists: pgsql-hackers 
On Sat, Feb 20, 2021 at 02:29:44PM +0530, Bharath Rupireddy wrote:
> Yeah. We could use pgstat_progress_update_multi_param instead of
> pgstat_progress_update_param to update multiple params.
> 
> On a quick scan through the code, I found that we can do the following. If
> okay, I can start a new thread so that we don't divert the main thread
> here. Thoughts?

Having a separate thread to discuss this part would be right.  This
way any patches sent would attract the correct audience.
--
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