Re: recovery is stuck when children are not processing SIGQUIT from previous crash

Поиск
Список
Период
Сортировка
От Marko Kreen
Тема Re: recovery is stuck when children are not processing SIGQUIT from previous crash
Дата
Msg-id e51f66da0911120734u2e65a031s5354e5fd133c4d73@mail.gmail.com
обсуждение исходный текст
Ответ на Re: recovery is stuck when children are not processing SIGQUIT from previous crash  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: recovery is stuck when children are not processing SIGQUIT from previous crash  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-admin
On 11/12/09, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Marko Kreen <markokr@gmail.com> writes:
>  > On 11/12/09, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>  >> The other thought is that quickdie should block signals before
>  >> starting to do anything.
>
>  > There would still be possibility of recursive syslog() calls.
>  > Shouldn't we fix that too?
>
>
> That's what the signal block would do.

usual elog
  syslog
<signal>
 quickdie
     block signals
     syslog

You talked about blocking in quickdie(), but you'd need
to block in elog().

--
marko

В списке pgsql-admin по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: recovery is stuck when children are not processing SIGQUIT from previous crash
Следующее
От: Tom Lane
Дата:
Сообщение: Re: recovery is stuck when children are not processing SIGQUIT from previous crash