Request a Demo
Home   >   mailing lists

Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows - Mailing list pgsql-bugs

From Andrew Dunstan
Subject Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
Date
Msg-id ae28b629-c48d-4752-aa89-d4cb3121ed08@dunslane.net
Whole thread
In response to Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
List pgsql-bugs
Tree view 
On 2026-10-08 Th 6:04 PM, David Rowley wrote:
> On Thu, 8 Oct 2026 at 21:30, Andrey Rachitskiy <pl0h0yp1@gmail.com> wrote:
>> Agreed. Skipping on es_epq_active was answering the wrong question.
>> The invariant is that InitExecPartitionPruneContexts() must not run
>> twice on a shared PartitionPruneState.
>> Your initialized flag is the right fix.
> Pushed.
>

per buildfarm, this is an ABI break on release 18, apparently needs an 
update to .abi-compliance-history


cheers


andrew


--
Andrew Dunstan
EDB: https://www.enterprisedb.com

pgsql-bugs by date:

Previous
From: Matthias van de Meent
Date:
Subject: Re: BUG #19519: REPACK can fail due to missing chunk for toast value
Next
From: Chinmay Kanchi
Date:
Subject: GIN disagrees with seq scan when NOT and AND operators are combined