Re: [Bug] Usage of stale dead_items pointer in parallel vacuum

John Naylor <johncnaylorls@gmail.com>

From: John Naylor <johncnaylorls@gmail.com>

To: Richard Guo <guofenglinux@gmail.com>

Cc: Kevin Oommen Anish <kevin.o@zohocorp.com>, pgsql-bugs <pgsql-bugs@lists.postgresql.org>

Date: 2025-10-02T05:09:47Z

Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix reuse-after-free hazard in dead_items_reset
- 76613b539ac5 18.1 landed
- 3549ffb6afaf 17.7 landed
- 54ab74865147 19 (unreleased) landed

On Thu, Oct 2, 2025 at 11:17 AM Richard Guo <guofenglinux@gmail.com> wrote:
> I can reproduce the issue and confirm that your patch fixes it.  I
> didn't use your custom malloc allocator but instead applied a
> redundant palloc0 for TidStore in TidStoreCreateShared(), hoping to
> get a different chunk of memory (haha).

I'm starting to wonder if we should have something similar to that
allocator in core, which is actually here and not in the link
upthread:

https://www.postgresql.org/message-id/193261e2c4d.3dd3cd7c1842.871636075166132237@zohocorp.com

-- 
John Naylor
Amazon Web Services