| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | 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:09:32 |
| Message-ID: | ed04b49c6bac6abba9b3830e7b6d852f77040bec.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
Is that repeatable?
If yes, it would be a bug.
If not, 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.
In the latter case, you can ignore the error.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-03-24 16:12:48 | Re: ERROR: could not attach to dynamic shared area |
| Previous Message | Adrian Klaver | 2021-03-24 15:18:04 | Re: No enough privileges for autovacuum worker |