Re: BUG #17619: AllocSizeIsValid violation in parallel hash join

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Dmitry Astapov <dastapov(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17619: AllocSizeIsValid violation in parallel hash join
Date: 2022-09-27 16:13:02
Message-ID: CAH2-Wz=+K9K+RYKLyDbPsp_gKfM_2YS-8zU4NxDY+EJ132cLMw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Sep 23, 2022 at 6:31 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> Uh, why is it okay that we don't zero-initialize memory used for
> things like PARALLEL_KEY_BUFFER_USAGE and PARALLEL_KEY_WAL_USAGE?

Ping? I'm pretty sure that this needs to be fixed.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2022-09-27 16:24:08 Re: BUG #17619: AllocSizeIsValid violation in parallel hash join
Previous Message Tom Lane 2022-09-27 15:51:45 Re: BUG #17385: "RESET transaction_isolation" inside serializable transaction causes Assert at the transaction end