From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephen Frost <sfrost@snowman.net>
cc: pgsql-hackers@lists.postgresql.org
Subject: "could not reattach to shared memory" on buildfarm member dory
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <25494.1524517820.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 23 Apr 2018 17:10:20 -0400
Message-ID: <25495.1524517820@sss.pgh.pa.us>
Precedence: bulk

So far, dory has failed three times with essentially identical symptoms:

2018-04-23 19:57:10.624 GMT [2240] FATAL:  could not reattach to shared me=
mory (key=3D0000000000000190, addr=3D00000000018E0000): error code 487
2018-04-23 15:57:10.657 EDT [8836] ERROR:  lost connection to parallel wor=
ker
2018-04-23 15:57:10.657 EDT [8836] STATEMENT:  select count(*) from tenk1 =
group by twenty;
2018-04-23 15:57:10.660 EDT [3820] LOG:  background worker "parallel worke=
r" (PID 2240) exited with exit code 1

Now how can this be?  We've successfully reserved and released the address
range we want to use, so it *should* be free at the instant we try to map.

Another thing that seems curious, though it may just be an artifact of
not having many data points yet, is that these failures all occurred
during pg_upgradecheck.  You'd think the "check" and "install-check"
steps would be equally vulnerable to the failure.

I guess the good news is that we're seeing this in a reasonably
reproducible fashion, so there's some hope of digging down to find
out the actual cause.

			regards, tom lane