Re: [PATCH] Initial progress reporting for COPY command

Fujii Masao <masao.fujii@oss.nttdata.com>

From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: Daniel Gustafsson <daniel@yesql.se>, Josef Šimánek <josef.simanek@gmail.com>
Cc: Tomas Vondra <tomas.vondra@2ndquadrant.com>, Pg Hackers <pgsql-hackers@postgresql.org>, Pavel Stehule <pavel.stehule@gmail.com>, vignesh C <vignesh21@gmail.com>
Date: 2020-07-28T17:00:04Z
Lists: pgsql-hackers

On 2020/07/02 21:51, Daniel Gustafsson wrote:
>> On 2 Jul 2020, at 14:42, Josef Šimánek <josef.simanek@gmail.com> wrote:
>> čt 2. 7. 2020 v 14:25 odesílatel Daniel Gustafsson <daniel@yesql.se <mailto:daniel@yesql.se>> napsal:
> 
>> The automated patchtester for the Commitfest gets confused when there are two
>> versions of the same changeset attached to the email, as it tries to apply them
>> both which obviously results in an application failure.  I've attached just the
>> previously submitted patch version to this email to see if we can get a test
>> run of it.
>>
>> Thanks, I'm new to commitfest and I was confused as well.
> 
> No worries, we're here to help.
> 
>> I tried to reattach the thread there. I'll prepare a new patch soon, what should I do? Just attach it again?

New patch has not been sent yet.
So I marked this as "Waiting on Author" at Commit Fest.

Regards,


-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION



Commits

  1. Report progress of COPY commands

  2. Doc fixup for hashagg_avoid_disk_plan GUC.

  3. Fix inconsistent markups in catalogs.sgml