Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xH95k-00000002qbw-0v9P for pgsql-bugs@arkaria.postgresql.org; Thu, 15 Oct 2026 00:13:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xH95i-000000064Dl-3WyN for pgsql-bugs@arkaria.postgresql.org; Thu, 15 Oct 2026 00:13:02 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xH95i-000000064Dc-2RtF for pgsql-bugs@lists.postgresql.org; Thu, 15 Oct 2026 00:13:02 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xH95g-000000029YA-0ZEh for pgsql-bugs@lists.postgresql.org; Thu, 15 Oct 2026 00:13:02 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.18.1/8.18.1) with ESMTP id 69F0Cj1k1727665; Wed, 14 Oct 2026 20:12:45 -0400 From: Tom Lane To: David Rowley cc: Andrew Dunstan , Andrey Rachitskiy , Vladimir Savin , =?utf-8?Q?=C3=81lvaro?= Herrera , pgsql-bugs@lists.postgresql.org Subject: Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows In-reply-to: References: Comments: In-reply-to David Rowley message dated "Mon, 12 Oct 2026 13:16:36 +1300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1727663.1792023165.1@sss.pgh.pa.us> Date: Wed, 14 Oct 2026 20:12:45 -0400 Message-ID: <1727664.1792023165@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk David Rowley writes: > On Sat, 10 Oct 2026 at 03:28, Andrew Dunstan wrote: >> per buildfarm, this is an ABI break on release 18, apparently needs an >> update to .abi-compliance-history > Thanks for highlighting that. I'll look at this once the RC1 commit > embargo is lifted. Seems Zsolt has uncovered a reason to warrant the > removal of the new flag. So it doesn't seem right to add the exception > if it'll disappear soon. Could we prioritize getting that straight? Alvaro's beff3cd00 et al have created an independent ABI break, but I don't think we can update .abi-compliance-history for that until this earlier issue is resolved. regards, tom lane