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

From: John Naylor <johncnaylorls(at)gmail(dot)com>
To: Richard Guo <guofenglinux(at)gmail(dot)com>
Cc: Kevin Oommen Anish <kevin(dot)o(at)zohocorp(dot)com>, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: [Bug] Usage of stale dead_items pointer in parallel vacuum
Date: 2025-10-02 05:09:47
Message-ID: CANWCAZbfPmrdAzsUn4X805dmmqTBmxMHk81wB9Z3Eb2AbCYtvw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Oct 2, 2025 at 11:17 AM Richard Guo <guofenglinux(at)gmail(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message White, Ian Keith 2025-10-02 08:32:02 RE: IN List operator , where list of values are over a number of lines
Previous Message Richard Guo 2025-10-02 04:16:47 Re: [Bug] Usage of stale dead_items pointer in parallel vacuum