Re: REL_11_STABLE: dsm.c - cannot unpin a segment that is not pinned
От | Justin Pryzby |
---|---|
Тема | Re: REL_11_STABLE: dsm.c - cannot unpin a segment that is not pinned |
Дата | |
Msg-id | 20190217203537.GC28750@telsasoft.com обсуждение исходный текст |
Ответ на | Re: REL_11_STABLE: dsm.c - cannot unpin a segment that is not pinned (Thomas Munro <thomas.munro@enterprisedb.com>) |
Ответы |
Re: REL_11_STABLE: dsm.c - cannot unpin a segment that is not pinned
|
Список | pgsql-hackers |
On Mon, Feb 18, 2019 at 09:26:53AM +1300, Thomas Munro wrote: > On Mon, Feb 18, 2019 at 9:07 AM Justin Pryzby <pryzby@telsasoft.com> wrote: > > Actually... > > > > On killing the postmaster having completed this stress test, one of the > > backends was left running and didn't die on its own. It did die gracefully > > when I killed the backend or the client. > > > > I was able to repeat the result, on first try, but took numerous attempts to > > repeat the 2nd and 3rd time to save pg_stat_activity. > > > > Is there some issue regarding dsm_postmaster_shutdown ? > > Huh. What exactly do you mean by "killing the postmaster"? If you > mean SIGKILL or something, one problem with 11 is that I mean unqualified /bin/kill which is kill -TERM (-15 in linux). I gather (pun acknowledged but not intended) you mean "one problem with PG v11" and not "one problem with kill -11" (which is what I first thought, although I was somehow confusing kill -9, and since I don't know why anyone would ever want to manually send SIGSEGV). I think you're suggesting that's a known issue with v11, so nothing to do. Thanks, Justin
В списке pgsql-hackers по дате отправления: