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: Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>
Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>, Luis Carril <luis.carril@swarm64.com>, "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-23T07:50:45Z
Lists: pgsql-bugs 
On Fri, Dec 21, 2018 at 04:51:23PM +0900, Michael Paquier wrote:
> The conflicts would be a bit annoying yes, still those are minimal so
> I would still use the macro on HEAD.  Let's see if others have an
> opinion.  We will have a divergence between v10 and v11 anyway as v11
> has added support for COPY with foreign tables, and v10 has added
> support for COPY with views.

Finally done and committed down to v10 as adapted.
--
Michael

Commits

  1. Disable WAL-skipping optimization for COPY on views

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