Re: BUG in 10.1 - dsa_area could not attach to a segment that hasbeen freed - Mailing list pgsql-bugs

From Thomas Munro
Subject Re: BUG in 10.1 - dsa_area could not attach to a segment that hasbeen freed
Date
Msg-id CAEepm=0VZbBmRD33uiTS5mM4c1tf7T_aH3tOb3isbXW+b9OrTQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG in 10.1 - dsa_area could not attach to a segment that hasbeen freed  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: BUG in 10.1 - dsa_area could not attach to a segment that hasbeen freed  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-bugs
On Wed, Nov 29, 2017 at 1:33 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> Why not?  Can't it just be that the workers are slow getting started?

In the normal non-error control flow, don't we expect
ExecShutdownGather() to run ExecParallelFinish() before
ExecParallelCleanup(), meaning that the leader waits for workers to
finish completely before it detaches itself?  Doesn't that need to be
case to avoid random "unable to map dynamic shared memory segment" and
"dsa_area could not attach to a segment that has been freed" errors,
and for the parallel instrumentation shown in EXPLAIN to be reliable?

Could it be that the leader thought that a worker didn't start up, but
in fact it did?

-- 
Thomas Munro
http://www.enterprisedb.com


pgsql-bugs by date:

Previous
From: Robert Haas
Date:
Subject: Re: BUG in 10.1 - dsa_area could not attach to a segment that hasbeen freed
Next
From: Michael Paquier
Date:
Subject: Re: [BUGS] Improper const-evaluation of HAVING with grouping sets andsubquery pullup