Re: BUG #16104: Invalid DSA Memory Alloc Request in Parallel Hash

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, James Coleman <jtc331(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16104: Invalid DSA Memory Alloc Request in Parallel Hash
Date: 2019-12-14 04:01:05
Message-ID: CA+hUKG+o1d5dMThbTTpCPUTJzx3FX2-TE=JRqgeEVQNo1wLfPg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Dec 11, 2019 at 6:32 AM Tomas Vondra
<tomas(dot)vondra(at)2ndquadrant(dot)com> wrote:
> The annoying thing is that it's the workers that crash, and the leader
> failed to notice that, so it was waiting in WaitForParallelWorkersToExit
> forever. Not sure what the issue is.

That's bad. Some edge case in
WaitForBackgroundWorkerShutdown()/GetBackgroundWorkerPid() that is
b0rked perhaps? Can you reproduce it, and tell us what the stack
looks like, maybe on a new thread?

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-12-14 04:05:38 Re: postgres has no spinlock support on riscv rv64imafdc
Previous Message PG Bug reporting form 2019-12-14 03:44:37 BUG #16165: Query Works fine but spam so many LOG: unrecognized win32 error code: 38