Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nFGpw-0007Vc-9d for pgsql-bugs@arkaria.postgresql.org; Wed, 02 Feb 2022 14:42:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nFGpu-0005Q5-W4 for pgsql-bugs@arkaria.postgresql.org; Wed, 02 Feb 2022 14:42:18 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nFGpt-0005Pq-Nq for pgsql-bugs@lists.postgresql.org; Wed, 02 Feb 2022 14:42:18 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nFGpm-0007ms-4d for pgsql-bugs@lists.postgresql.org; Wed, 02 Feb 2022 14:42:17 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 61C135C018B; Wed, 2 Feb 2022 09:42:06 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Wed, 02 Feb 2022 09:42:06 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=aW4J7TWM84dlfQu1XeIGotpXuY387v4v1XFgXA+HkSc=; b=Mnkh3gOR k2eeH5jQAJpQcVXF9EIygRBh6ruBWWr2ANPTwkyRJiqPWn8GcLA0PsKj+Qw0wpcL +TOxdqCebhQAfAClY4/UpZINTbWl7Oqb/noTB27WXRmoHtbwnrnd4HmoFD11dzZ9 YYLyc/atIp6rv8p0Snt7zdiU0p3ORrADKVwH0Lodh+IPMcgpmJnyN3UiEJGLQods BVjeuc2Y+/A4Q5FOyt4HwZKhKz3udUVThkEvc9jspSy6Qbt50Khb9Pu0dyRblwta 8KC8OLD/vdOWP1xU4X2N0sJ3xx+6WrDhqO6uIh9PxcExvyGpKtNxjhgrIqek+HAI MK+2BiEQa/KwYA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrgeehgdeikecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkgggtugfgjgesthekredttddtjeenucfhrhhomheptehlvhgrrhho ucfjvghrrhgvrhgruceorghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgheqne cuggftrfgrthhtvghrnhepvdekuddvveeltdduhfetgeefgedvgffgleekfefhffegtedu leelkefgvddvteffnecuffhomhgrihhnpegvnhhtvghrphhrihhsvggusgdrtghomhdpth ifihhtthgvrhdrtghomhenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgr ihhlfhhrohhmpegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 2 Feb 2022 09:42:05 -0500 (EST) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 3350A2A0DF6; Wed, 2 Feb 2022 11:42:02 -0300 (-03) Date: Wed, 2 Feb 2022 11:42:02 -0300 From: Alvaro Herrera To: Etsuro Fujita Cc: Alexander Lakhin , pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17355: Server crashes on ExecReScanForeignScan in postgres_fdw when accessing foreign partition Message-ID: <202202021442.hsxbhre2k533@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2022-Feb-01, Etsuro Fujita wrote: > I didn’t include your test because in my > understanding we don’t add such a test into the postgres_fdw > regression test. I’ll commit the patch if there are no objections > from you (or anyone else). I think it would be good to reconsider this. We currently don't have any isolation test files for postgres_fdw, but that doesn't mean we can't add some (we now have several subdirs where both types of tests coexist). And if we don't have these tests, it will be easier to break this again in the future without noticing if we decide to rework executor code again, which I'm sure we'll do. Maybe you don't need to add the test in back-branches, which is more work; but if you only target branch master, it should only require an ISOLATION line in the Makefile listing the new test. -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/ "Every machine is a smoke machine if you operate it wrong enough." https://twitter.com/libseybieda/status/1541673325781196801