Re: pg11.1: dsa_area could not attach to segment

Thomas Munro <thomas.munro@enterprisedb.com>

From: Thomas Munro <thomas.munro@enterprisedb.com>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: Sergei Kornilov <sk@zsrv.org>, "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>
Date: 2019-02-12T05:33:31Z
Lists: pgsql-hackers
On Tue, Feb 12, 2019 at 4:27 PM Thomas Munro
<thomas.munro@enterprisedb.com> wrote:
> On Tue, Feb 12, 2019 at 4:01 PM Justin Pryzby <pryzby@telsasoft.com> wrote:
> > On Mon, Feb 11, 2019 at 08:43:14PM -0600, Justin Pryzby wrote:
> > > I have a suspicion that this doesn't happen if
> > > parallel_leader_participation=off.
> >
> > I think this is tentatively confirmed..I ran 20 loops for over 90 minutes with
> > no crash when parallel_leader_participation=off.
> >
> > On enabling parallel_leader_participation, crash within 10min.
>
> That's quite interesting.  I wonder if it's something specific about
> the leader's behaviour, or if it's just because it takes one more
> process to hit the bad behaviour on your system.

.  o O ( is there some way that getting peppered with signals from the
shm tuple queue machinery could break something here? )

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


Commits

  1. Fix race in dsm_attach() when handles are reused.

  2. Refactor pid, random seed and start time initialization.