Re: Improvements and additions to COPY progress reporting - Mailing list pgsql-hackers

From Matthias van de Meent
Subject Re: Improvements and additions to COPY progress reporting
Date
Msg-id CAEze2Wh_ohsJuRQ7kkCnfZWNqHXLsJCFsKzRauoGNeNgG=eosg@mail.gmail.com
Whole thread Raw
In response to Re: Improvements and additions to COPY progress reporting  (Matthias van de Meent <boekewurm+postgres@gmail.com>)
Responses Re: Improvements and additions to COPY progress reporting
List pgsql-hackers
On Fri, 12 Feb 2021 at 12:23, Matthias van de Meent
<boekewurm+postgres@gmail.com> wrote:
>
> On Thu, 11 Feb 2021 at 15:44, Bharath Rupireddy
> <bharath.rupireddyforpostgres@gmail.com> wrote:
> >
> >
> > On Thu, Feb 11, 2021, 8:08 PM Josef Šimánek <josef.simanek@gmail.com> wrote:
> >> I have split it since it should be the start of progress reporting
> >> testing at all. If you better consider this as part of COPY testing,
> >> feel free to move it to already existing copy testing related files.
> >> There's no real reason to keep it separated if not needed.
> >
> >
> > +1 to move those test cases to existing copy test files.
>
> Thanks for your reviews. PFA v4 of the patchset, in which the tests
> are put into copy.sql (well, input/copy.source). This also adds tests
> for correctly reporting COPY ... FROM 'file'.

PFA v5, which fixes a failure in the pg_upgrade regression tests due
to incorrect usage of @abs_builddir@. I had the changes staged, but
forgot to add them to the patches.

Sorry for the noise.

-Matthias

Attachment

pgsql-hackers by date:

Previous
From: Zhihong Yu
Date:
Subject: Re: Parallel INSERT (INTO ... SELECT ...)
Next
From: Erik Rijkers
Date:
Subject: logical replication seems broken