Horton

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

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Cc: Luis Carril <luis.carril@swarm64.com>, Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>, PG Bug reporting form <noreply@postgresql.org>, Michael Paquier <michael.paquier@gmail.com>
Date: 2018-12-19T04:04:14Z
Lists: pgsql-bugs 
On Wed, Dec 19, 2018 at 01:01:01PM +0900, Amit Langote wrote:
> It may happen sooner that you may think. :)
> 
> Currently, COPY into foreign tables uses APIs used by INSERT, so one row
> at a time interface.  It'd certainly be better to allow FDWs to be able to
> do bulk transfer.  I think Fujita-san has said he wants to work on that:
> 
> https://www.postgresql.org/message-id/5AB4F190.1000804%40lab.ntt.co.jp

That's interesting.

>> One argument for doing nothing yet is that
>> this command does not fail now so changing it may cause compatibility
>> problems.
> 
> Just FYI, COPYing into foreign tables is only supported as of PG 11.

Which has already been released..  Anyway.
--
Michael

Commits

  1. Disable WAL-skipping optimization for COPY on views

  2. Disable WAL-skipping optimization for COPY on views and foreign tables