| From: | Sergei Kornilov <sk(at)zsrv(dot)org> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg11.1: dsa_area could not attach to segment |
| Date: | 2019-02-14 16:36:55 |
| Message-ID: | 142271550162215@sas1-cd55e40a6ba0.qloud-c.yandex.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi
> Do you think that plausibly explains and resolves symptoms of bug#15585, too?
I think yes. Bug#15585 raised only after "dsa_area could not attach to segment" in different parallel worker. Leader stuck because waiting all parallel workers, but one worker has unexpected recursion in dsm_backend_shutdown [1] and will never shutdown. Backtrace show previous error in this backend: "cannot unpin a segment that is not pinned" - root cause is earlier and in a different process.
* https://www.postgresql.org/message-id/70942611548327380%40myt6-7734411c649e.qloud-c.yandex.net
regards, Sergei
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-02-14 16:43:05 | Inconsistencies between dependency.c and objectaddress.c |
| Previous Message | Justin Pryzby | 2019-02-14 16:20:10 | Re: pg11.1: dsa_area could not attach to segment |