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 1nGj2B-0007jJ-DW for pgsql-bugs@arkaria.postgresql.org; Sun, 06 Feb 2022 15:00:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nGj29-0007y9-BD for pgsql-bugs@arkaria.postgresql.org; Sun, 06 Feb 2022 15:00:57 +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 1nGj29-0007y0-3D for pgsql-bugs@lists.postgresql.org; Sun, 06 Feb 2022 15:00:57 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nGj26-0003fY-OI for pgsql-bugs@lists.postgresql.org; Sun, 06 Feb 2022 15:00:56 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id A44505C00A4; Sun, 6 Feb 2022 10:00:53 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Sun, 06 Feb 2022 10:00:53 -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=UT1PbSRJnER2Jq4G4FhGSwSiYSxuf5Yy7bAJvSxZxDA=; b=XlfuI+NN OYQZTS1zULlXeQdIu+T2T6lzwGuhhInozQh6y9Nb+Gue/50TeMDa5++Pa2BuKJSM oJSix75QU15z5Q0CrW1EhxkCQCagzeZziYBF0vvRzUoujxbjvk+jQeUlDYfFXTEu 5dGmNfNjIBHPfvHD1OTrs0T6eZhBduYrfEadhGcvCMvcB3EUPZwm/l1glaxNljeY APLXFeb6/eCUHnU9o1clVhg8aXfyDYZQ/vhqNU3eGjbxMwwsijdIiWfCS5FBZSqH YBrncA3kPeWVLXltdtVENtNfdmZM4XD6DbqnGkdfvQ075QRE76tKGDrEK3iE4mQf jaQVroK0tH+FNg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrheefgdejvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkgggtugfgjgesthekredttddtjeenucfhrhhomheptehlvhgrrhho ucfjvghrrhgvrhgruceorghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgheqne cuggftrfgrthhtvghrnhepudejveejffejveduudetvdekieeuiedtvdeileefkeevjedu feeguedvjefhueelnecuffhomhgrihhnpegvnhhtvghrphhrihhsvggusgdrtghomhenuc evlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhvhhgv rhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 6 Feb 2022 10:00:52 -0500 (EST) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 8CB302A0664; Sun, 6 Feb 2022 12:00:50 -0300 (-03) Date: Sun, 6 Feb 2022 12:00:50 -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: <202202061500.ocwvfbkylw3g@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-03, Etsuro Fujita wrote: > > 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. > > I think it would be better to create a separate patch so that we test > not only this but other EvalPlanQual stuff such as ForeignRecheck, so > I applied the proposed patch to HEAD as well. Sure, that sounds good. Are you or is anybody else working on that? -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/ Maybe there's lots of data loss but the records of data loss are also lost. (Lincoln Yeoh)