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 Andrey Rachitskiy
Subject Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
Date
Msg-id CAB8bMis2F4JpZnWzc6Y7p7F1u5fUR07M_kPt-y7XaoLF965=2w@mail.gmail.com
Whole thread
In response to Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows  (Vladimir Savin <vladimir@encord.com>)
Responses Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows
List pgsql-bugs
Tree view

пт, 2 окт. 2026 г. в 00:36, Vladimir Savin <vladimir@encord.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

pgsql-bugs by date:

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