From: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(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-03-08 16:33:40 |
Message-ID: | CAEze2WgNOwPGo1HyApSxqovsUhtsQSc6sH-1kDFuCR-v_BdTGg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 8 Mar 2021 at 09:24, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Sun, Mar 07, 2021 at 04:50:31PM +0530, Bharath Rupireddy wrote:
> > Attaching remaining patches 0001 and 0003 from the v11 patch
> > set(posted upthread) here to make cfbot happier.
>
> Looking at patch 0002, the location of each progress report looks good
> to me. I have some issues with some of the names chosen though, so I
> would like to suggest a few changes to simplify things:
> - PROGRESS_COPY_IO_TYPE_* => PROGRESS_COPY_TYPE_*
> - PROGRESS_COPY_IO_TYPE => PROGRESS_COPY_TYPE
> - PROGRESS_COPY_TYPE_STDIO => PROGRESS_COPY_TYPE_PIPE
> - In pg_stat_progress_copy, io_type => type
Seems reasonable. PFA updated patches. I've renamed the previous 0003
to 0002 to keep git-format-patch easy.
> It seems a bit confusing to not count insertions on foreign tables
> where nothing happened. I am fine to live with that, but can I ask if
> this has been thought about?
This is keeping current behaviour of the implementation as committed
with 8a4f618e, with the rationale of that patch being that this number
should mirror the number returned by the copy command.
I am not opposed to adding another column for `tuples_inserted` and
changing the logic accordingly (see prototype 0003), but that was not
in the intended scope of this patchset. Unless you think that this
should be included in this current patchset, I'll spin that patch out
into a different thread, but I'm not sure that would make it into
pg14.
With regards,
Matthias van de Meent.
Attachment | Content-Type | Size |
---|---|---|
v12-0003-Adapt-COPY-progress-reporting-to-report-processe.txt | text/plain | 10.7 KB |
v12-0001-Additional-progress-reported-components-for-COPY.patch | text/x-patch | 12.4 KB |
v12-0002-Add-copy-progress-reporting-regression-tests.patch | text/x-patch | 5.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2021-03-08 16:35:56 | Re: pg_upgrade failing for 200+ million Large Objects |
Previous Message | Tom Lane | 2021-03-08 16:33:02 | Re: pg_upgrade failing for 200+ million Large Objects |