| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Albrecht Dreß <albrecht(dot)dress(at)netcologne(dot)de>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: ERROR: could not attach to dynamic shared area |
| Date: | 2021-03-24 16:12:48 |
| Message-ID: | 1100686.1616602368@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Carlos Montenegro | 2021-03-24 17:17:31 | Hello - About how to install PgAdmin4 on Debian 10 |
| Previous Message | Laurenz Albe | 2021-03-24 16:09:32 | Re: ERROR: could not attach to dynamic shared area |