Re: Improvements and additions to COPY progress reporting
Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
From: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
To: Matthias van de Meent <boekewurm+postgres@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Tomas Vondra <tomas.vondra@enterprisedb.com>, Josef Šimánek <josef.simanek@gmail.com>
Date: 2021-02-10T06:43:08Z
Lists: 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
Commits
-
Add some basic tests for progress reporting of COPY
- 15639d5e8f6f 14.0 landed
-
Add support for more progress reporting in COPY
- 9d2d45700928 14.0 landed
-
doc: Add backlinks to progress reporting documentation
- 8a8f4d8ede28 14.0 landed