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

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Andrey Rachitskiy <pl0h0yp1(at)gmail(dot)com>
Cc: 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-08 22:04:56
Message-ID: CAApHDvpFu3C5XK4J1LUdgDPpp-G+VkqLr+ZRFZ6oTMDaXLwkBw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, 8 Oct 2026 at 21:30, Andrey Rachitskiy <pl0h0yp1(at)gmail(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Previous Message Jacob Champion 2026-10-08 21:28:19 Re: Do we want to solve reload/config races more generally? (was: Postmaster crashes on SIGHUP when oauth_validator_libraries holds only whitespace)