| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| 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 00:12:45 |
| Message-ID: | 1727664.1792023165@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> 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.
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2026-10-15 01:25:54 | Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows |
| Previous Message | Manu | 2026-10-14 22:53:18 | Re: VACUUM/ANALYZE double-count the backend's own pending table stats |