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

From Robert Haas
Subject Re: BUG in 10.1 - dsa_area could not attach to a segment that hasbeen freed
Date
Msg-id CA+Tgmob=UfOwbJCP9QVAQVSo0LPq8t-w-BtoRKDTzDGzmVZUbA@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  (Thomas Munro <thomas.munro@enterprisedb.com>)
Responses Re: BUG in 10.1 - dsa_area could not attach to a segment that hasbeen freed  (Thomas Munro <thomas.munro@enterprisedb.com>)
List pgsql-bugs
On Tue, Nov 28, 2017 at 7:04 PM, Thomas Munro
<thomas.munro@enterprisedb.com> wrote:
> Hmm.  Well, it's the same error message but I don't think it's the
> same: that other thread was about C extension code using APIs
> incorrectly.  This is parallel query, which shouldn't reach that error
> unless all the backends detach before one backend tries to attach,
> which I wouldn't normally expect to happen unless something else went
> wrong first.

Why not?  Can't it just be that the workers are slow getting started?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-bugs by date:

Previous
From: Thomas Munro
Date:
Subject: Re: BUG in 10.1 - dsa_area could not attach to a segment that hasbeen freed
Next
From: Thomas Munro
Date:
Subject: Re: BUG in 10.1 - dsa_area could not attach to a segment that hasbeen freed