Re: [PATCH] Initial progress reporting for COPY command - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: [PATCH] Initial progress reporting for COPY command
Date
Msg-id d32112b9-6533-0d0d-fe18-e252d4adc359@oss.nttdata.com
Whole thread Raw
In response to Re: [PATCH] Initial progress reporting for COPY command  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: [PATCH] Initial progress reporting for COPY command  (Josef Šimánek <josef.simanek@gmail.com>)
List 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



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: 13dev failed assert: comparetup_index_btree(): ItemPointer values should never be equal
Next
From: Justin Pryzby
Date:
Subject: [PATCH] Tab completion for VACUUM of partitioned tables