From: Tom Lane <tgl@sss.pgh.pa.us>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Albrecht Dreß <albrecht.dress@netcologne.de>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: ERROR: could not attach to dynamic shared area
Date: Wed, 24 Mar 2021 12:12:48 -0400
Message-ID: <1100686.1616602368@sss.pgh.pa.us> (raw)
In-Reply-To: <ed04b49c6bac6abba9b3830e7b6d852f77040bec.camel@cybertec.at>
References: <XKUSPZTU.PDRSNWRY.QVVL7KCF@4DGOL2RI.4CELUPIY.V55SIPQJ>
<ed04b49c6bac6abba9b3830e7b6d852f77040bec.camel@cybertec.at>
Laurenz Albe <laurenz.albe@cybertec.at> writes:
> On Wed, 2021-03-24 at 09:01 +0100, Albrecht Dreß wrote:
>> in the logs of my database server, I found the following message:
>>> ERROR: could not attach to dynamic shared area
>>> LOG: background worker "parallel worker" (PID 51151) exited with exit code 1
> ... it could be a race condition: a parallel query finished rather fast,
> but one of the parallel workers took long to start up, so when it tries to
> attach to the dynamic shared memory segment used to exchange data between the
> parallel processes, it realizes that everybody else has already left and
> destroyed the memory segment.
If the error only appeared in the log, and wasn't reported to the
client, then this theory seems pretty plausible.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-general@postgresql.org
Cc: tgl@sss.pgh.pa.us, laurenz.albe@cybertec.at, albrecht.dress@netcologne.de, pgsql-general@lists.postgresql.org
Subject: Re: ERROR: could not attach to dynamic shared area
In-Reply-To: <1100686.1616602368@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox