Re: Improvements and additions to COPY progress reporting
Tomas Vondra <tomas.vondra@enterprisedb.com>
From: Tomas Vondra <tomas.vondra@enterprisedb.com>
To: Matthias van de Meent <boekewurm+postgres@gmail.com>,
Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Cc: Josef Šimánek <josef.simanek@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2021-02-15T16:07:11Z
Lists: pgsql-hackers
Attachments
Hi, I agree with these changes in general - I have a couple minor comment: 1) 0001 - the SGML docs are missing a couple tags - The blocks in copyfrom.cc/copyto.c should be reworked - I don't think we do this in our codebase. Move the variable declarations to the beginning, get rid of the out block. Or something like that. - I fir the "io_target" name misleading, because in some cases it's actually the *source*. 2) 0002 - I believe "each backend ... reports its" (not theirs), right? - This seems more like a generic docs improvement, not quite specific to the COPY progress patch. It's a bit buried, maybe it should be posted separately. OTOH it's pretty small. 3) 0003 - Some whitespace noise, triggering "git am" warnings. - Might be good to briefly explain what the regression test does with the triggers, etc. regards -- Tomas Vondra EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
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