Re: Add guc to enable send SIGSTOP to peers when backend exits abnormally
От | Tom Lane |
---|---|
Тема | Re: Add guc to enable send SIGSTOP to peers when backend exits abnormally |
Дата | |
Msg-id | 2498875.1630679973@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Add guc to enable send SIGSTOP to peers when backend exits abnormally ("蔡梦娟(玊于)" <mengjuan.cmj@alibaba-inc.com>) |
Ответы |
Re: Add guc to enable send SIGSTOP to peers when backend exits abnormally
|
Список | pgsql-hackers |
"=?UTF-8?B?6JSh5qKm5aifKOeOiuS6jik=?=" <mengjuan.cmj@alibaba-inc.com> writes: > I want to share a patch with you, in which I add a guc parameter 'enable_send_stop' to enable set the value of SendStopin postmaster.c more conveniently. SendStop enable postmaster to send SIGSTOP rather than SIGQUIT to its childrenwhen some backend dumps core, and this variable is originally set with -T parameter when start postgres, which isinconvenient to control in some scenarios. TBH, I'd sooner rip out SendStop, and simplify the related postmaster logic. I've never used it in twenty-some years of Postgres hacking, and I doubt anyone else has used it much either. It's not worth the overhead of a GUC. (The argument that you need it in situations where you can't control the postmaster's command line seems pretty thin, too. I'm much more worried about somebody turning it on by accident and then complaining that the cluster freezes upon crash.) regards, tom lane
В списке pgsql-hackers по дате отправления: