Horton

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

Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>

View thread View on postgr.es
From: Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>
To: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Cc: Michael Paquier <michael@paquier.xyz>, 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-25T01:48:05Z
Lists: pgsql-bugs 
(2018/12/25 9:50), Amit Langote wrote:
> On 2018/12/24 16:08, Michael Paquier wrote:
>> On Sun, Dec 23, 2018 at 04:50:45PM +0900, Michael Paquier wrote:
>>> Finally done and committed down to v10 as adapted.
>>
>> Just for the note: I have switched my buildfarm animal dangomushi to
>> use wal_level = minimal as server configuration for the main
>> regression tests so as the new tests get stressed for all the branches
>> tested (down to v10).
>
> Thank you, Michael.

Many thanks!

Best regards,
Etsuro Fujita

Commits

  1. Disable WAL-skipping optimization for COPY on views

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