Re: BUG #17619: AllocSizeIsValid violation in parallel hash join - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: BUG #17619: AllocSizeIsValid violation in parallel hash join
Date
Msg-id CAH2-Wzk+wEsNxXJwt=jHpExbBFh+vLnyfJ7CcNqMmnGkiQvFKw@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17619: AllocSizeIsValid violation in parallel hash join  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #17619: AllocSizeIsValid violation in parallel hash join
List pgsql-bugs
On Fri, Sep 23, 2022 at 4:19 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> That's a fairly scary observation.  What other places are silently
> expecting such memory to be zeroed?  Do we need to fix things so
> that min_dynamic_shared_memory doesn't break this API?

Reminds me of the recent parallel VACUUM bug, fixed by commit
662ba729. That involved unintialized DSM, too.

As I said at the time: we should be using Valgrind for this.

-- 
Peter Geoghegan



pgsql-bugs by date:

Previous
From: Thomas Munro
Date:
Subject: Re: BUG #17619: AllocSizeIsValid violation in parallel hash join
Next
From: Richard Guo
Date:
Subject: Re: BUG #17618: unnecessary filter column <> text even after adding index