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 David Rowley
Subject Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
Date
Msg-id CAApHDvpFu3C5XK4J1LUdgDPpp-G+VkqLr+ZRFZ6oTMDaXLwkBw@mail.gmail.com
Whole thread
In response to Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows  (Andrey Rachitskiy <pl0h0yp1@gmail.com>)
Responses Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
List pgsql-bugs
Tree view 
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.

David

pgsql-bugs by date:

Previous
From: Andrey Rachitskiy
Date:
Subject: Re: BUG #19752: GROUP BY on a constant and a cast to a length-limited array type crashes the server while planning
Next
From: Michael Ries
Date:
Subject: Bug in statement trigger for MERGE operations that move rows between partitions