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

From Bharath Rupireddy
Subject Re: Improvements and additions to COPY progress reporting
Date
Msg-id CALj2ACUCASUO9Le2Lq6d_gEdHtVEH6EFG19R-kKTWtRf2TmnVw@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 Tue, Feb 9, 2021 at 6:02 PM Matthias van de Meent
<boekewurm+postgres@gmail.com> wrote:
> > Also, you can add this to the current commitfest.
>
> See https://commitfest.postgresql.org/32/2977/
>
> On Tue, 9 Feb 2021 at 12:53, Josef Šimánek <josef.simanek@gmail.com> wrote:
> >
> > OK, would you mind to integrate my regression test initial patch as
> > well in v3 or should I submit it later in a separate way?
>
> Attached, with minor fixes

Why do we need to have a new test file progress.sql for the test
cases? Can't we add them into existing copy.sql or copy2.sql? Or do
you have a plan to add test cases into progress.sql for other progress
reporting commands?

IMO, it's better not add any new test file but add the tests to existing files.

With Regards,
Bharath Rupireddy.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: repeated decoding of prepared transactions
Next
From: "tsunakawa.takay@fujitsu.com"
Date:
Subject: RE: Parallel INSERT (INTO ... SELECT ...)