Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Andrey Rachitskiy <pl0h0yp1(at)gmail(dot)com>, Vladimir Savin <vladimir(at)encord(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
Date: 2026-10-12 00:16:36
Message-ID: CAApHDvoOTNzqrM4_UzohwfTAEA6CNd48o+1Bcbaj-odfrSMMkg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, 10 Oct 2026 at 03:28, Andrew Dunstan <andrew(at)dunslane(dot)net> 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.

David

In response to

Browse pgsql-bugs by date

  From Date Subject
Previous Message Tom Lane 2026-10-11 18:05:21 Re: GIN (JSONPath) checks equality only on the first node of each operand