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

From: Andrey Rachitskiy <pl0h0yp1(at)gmail(dot)com>
To: Vladimir Savin <vladimir(at)encord(dot)com>
Cc: 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-02 08:04:03
Message-ID: CAB8bMis2F4JpZnWzc6Y7p7F1u5fUR07M_kPt-y7XaoLF965=2w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

пт, 2 окт. 2026 г. в 00:36, Vladimir Savin <vladimir(at)encord(dot)com>:

>
> Is there anything else I can do to help, or are we all set?
>
>
Hi, Vladimir!

The patch fixes the issue, and now we just need someone to review and
approve it. So at this point we just have to wait for the maintainers to
take a look when they have time.

Also, a small request for future threads: please reply inline
(bottom-posting) — trim quotes and answer below the relevant part.

Thanks!

--
Regards,
Rachitskiy Andrey

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Vladimir Savin 2026-10-02 08:12:31 Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
Previous Message Andrey Rachitskiy 2026-10-02 07:57:48 Re: Backend crash (signal 11) in pg_trgm makesign() after ALTER TABLE ... SET STORAGE on a column with a gist_trgm_ops index