Re: pg11.1: dsa_area could not attach to segment - Mailing list pgsql-hackers

From Sergei Kornilov
Subject Re: pg11.1: dsa_area could not attach to segment
Date
Msg-id 142271550162215@sas1-cd55e40a6ba0.qloud-c.yandex.net
Whole thread Raw
In response to Re: pg11.1: dsa_area could not attach to segment  (Justin Pryzby <pryzby@telsasoft.com>)
Responses Re: pg11.1: dsa_area could not attach to segment  (Thomas Munro <thomas.munro@enterprisedb.com>)
List 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
stuckbecause waiting all parallel workers, but one worker has unexpected recursion in dsm_backend_shutdown [1] and will
nevershutdown. Backtrace show previous error in this backend: "cannot unpin a segment that is not pinned" - root cause
isearlier and in a different process.
 

* https://www.postgresql.org/message-id/70942611548327380%40myt6-7734411c649e.qloud-c.yandex.net

regards, Sergei


pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: pg11.1: dsa_area could not attach to segment
Next
From: Tom Lane
Date:
Subject: Inconsistencies between dependency.c and objectaddress.c