| From: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
|---|---|
| To: | Richard Guo <guofenglinux(at)gmail(dot)com> |
| Cc: | Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Use-after-free of a shared Path in add_path()/add_partial_path() |
| Date: | 2026-09-15 04:15:21 |
| Message-ID: | CAExHW5ur6z6u1OeYC8m6x500y-fBj5tFTicZC6Dz5FCJe=WWZQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Sep 15, 2026 at 8:35 AM Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
>
> The alternatives are a flat copy of Path, and reference counting (and
> maybe more). Copying also fixes the bug, so maybe it would be a
> workable solution too. Reference counting is more appealing in
> principle, but I think it's far too large a change to back-patch.
>
> Thoughts?
FWIW, we discussed reference counting paths in [1]. It is invasive. We
had seen a similar report around that time or that thread references a
thread with a similar bug as this thread.
[1] https://www.postgresql.org/message-id/CAExHW5tUcVsBkq9qT%3DL5vYz4e-cwQNw%3DKAGJrtSyzOp3F%3DXacA%40mail.gmail.com
--
Best Wishes,
Ashutosh Bapat
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shihao zhong | 2026-09-15 04:20:35 | Re: REPACK enhancements |
| Previous Message | shihao zhong | 2026-09-15 03:45:28 | Re: GIN index fast list search may become un-interruptible for long time. |