Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gZWX3-0003a1-IW for pgsql-bugs@arkaria.postgresql.org; Wed, 19 Dec 2018 07:44:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gZWX2-0007CR-8t for pgsql-bugs@arkaria.postgresql.org; Wed, 19 Dec 2018 07:44:40 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gZWX1-00073v-Vj for pgsql-bugs@lists.postgresql.org; Wed, 19 Dec 2018 07:44:40 +0000 Received: from tama50.ecl.ntt.co.jp ([129.60.39.147]) by makus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gZWWy-00043J-Ik; Wed, 19 Dec 2018 07:44:38 +0000 Received: from vc2.ecl.ntt.co.jp (vc2.ecl.ntt.co.jp [129.60.86.154]) by tama50.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id wBJ7iZWr029384; Wed, 19 Dec 2018 16:44:35 +0900 Received: from vc2.ecl.ntt.co.jp (localhost [127.0.0.1]) by vc2.ecl.ntt.co.jp (Postfix) with ESMTP id 9646963914D; Wed, 19 Dec 2018 16:44:35 +0900 (JST) Received: from jcms-pop21.ecl.ntt.co.jp (jcms-pop21.ecl.ntt.co.jp [129.60.87.134]) by vc2.ecl.ntt.co.jp (Postfix) with ESMTP id 94BFE63914A; Wed, 19 Dec 2018 16:44:35 +0900 (JST) Received: from [IPv6:::1] (unknown [129.60.241.75]) by jcms-pop21.ecl.ntt.co.jp (Postfix) with ESMTPSA id 8E5C1400AB7; Wed, 19 Dec 2018 16:44:35 +0900 (JST) Message-ID: <5C19F6E8.5080904@lab.ntt.co.jp> Date: Wed, 19 Dec 2018 16:44:40 +0900 From: Etsuro Fujita User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 Subject: Re: BUG #15552: Unexpected error in COPY to a foreign table in a transaction References: <15552-c64aa14c5c22f63c@postgresql.org> <8e82d10d-cc16-eed4-7634-3654f59d8053@lab.ntt.co.jp> <30718b48-8020-329a-c6f0-74e1222e5283@lab.ntt.co.jp> <5C18ECBB.2000507@lab.ntt.co.jp> <1c23a9b1-c9c0-a11a-63fc-d821602455ba@lab.ntt.co.jp> In-Reply-To: <1c23a9b1-c9c0-a11a-63fc-d821602455ba@lab.ntt.co.jp> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-CC-Mail-RelayStamp: 1 To: Amit Langote Cc: Luis Carril , "pgsql-bugs@lists.postgresql.org" , PG Bug reporting form X-TM-AS-MML: disable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk (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