Re: BUG #15552: Unexpected error in COPY to a foreign table in a transaction

From: Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>
To: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
Cc: Luis Carril <luis(dot)carril(at)swarm64(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>, PG Bug reporting form <noreply(at)postgresql(dot)org>
Subject: Re: BUG #15552: Unexpected error in COPY to a foreign table in a transaction
Date: 2018-12-19 07:44:40
Message-ID: 5C19F6E8.5080904@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

(2018/12/19 9:44), Amit Langote wrote:
> On 2018/12/18 21:48, Etsuro Fujita wrote:
>> FDWs would not look at heap_insert options, so another option would be to
>> 1) leave that options as-is for foreign tables and 2) if the target is a
>> foreign table, just skip heap_sync at the bottom of CopyFrom, or just
>> return without doing anything in heap_sync.
>
> 1 might be better because it both fixes the problem
> at hand and doesn't lead to misleadingly setting heap_insert options.

Yeah, that's the reason why I mentioned this.

Best regards,
Etsuro Fujita

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Etsuro Fujita 2018-12-19 07:49:19 Re: BUG #15552: Unexpected error in COPY to a foreign table in a transaction
Previous Message Srimal | PickMe 2018-12-19 06:19:53 Undefined symbol error - psql CLI client