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

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Andrey Rachitskiy <pl0h0yp1(at)gmail(dot)com>, Vladimir Savin <vladimir(at)encord(dot)com>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, 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-15 01:25:54
Message-ID: CAApHDvotJ1Ch=C=AR_1qOGJ8RewU6YjPkj6DPpRPi_5ZWCW7jg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, 15 Oct 2026 at 13:12, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.

It's on my list for today.

David

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message John Naylor 2026-10-15 02:44:09 use-after-free in jsonb_set_lax()
Previous Message Tom Lane 2026-10-15 00:12:45 Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows