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 1ivmdP-0005kO-Jh for pgsql-bugs@arkaria.postgresql.org; Sun, 26 Jan 2020 18:27:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ivmcO-00081I-8U for pgsql-bugs@arkaria.postgresql.org; Sun, 26 Jan 2020 18:26:44 +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 1ivmcN-0007we-Sv for pgsql-bugs@lists.postgresql.org; Sun, 26 Jan 2020 18:26:44 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ivmcG-0005Fr-JQ for pgsql-bugs@lists.postgresql.org; Sun, 26 Jan 2020 18:26:41 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 00QIQXgN012803; Sun, 26 Jan 2020 13:26:33 -0500 From: Tom Lane To: =?UTF-8?B?THVrw6HFoSBTb2JvdGth?= cc: pgsql-bugs@lists.postgresql.org Subject: Re: Segfault on updating foreign table In-reply-to: References: Comments: In-reply-to =?UTF-8?B?THVrw6HFoSBTb2JvdGth?= message dated "Sun, 26 Jan 2020 08:00:00 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <12801.1580063193.1@sss.pgh.pa.us> Date: Sun, 26 Jan 2020 13:26:33 -0500 Message-ID: <12802.1580063193@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk =?UTF-8?B?THVrw6HFoSBTb2JvdGth?= writes: > I tried to synchronize two tables on different databases using foreign data > wrapper. I executed update of foreign table with sub-query selection from > local table. As the result I got segmentation fault. General query: > UPDATE foreign_table SET (col) = ( > SELECT col > FROM local_table > WHERE foreign_table.id = local_table.id > ); Yup, that's a bug. Will fix, thanks for the report! regards, tom lane