Re: "stuck spinlock"

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: "stuck spinlock"
Дата
Msg-id 20131214122348.GC25520@awork2.anarazel.de
обсуждение исходный текст
Ответ на Re: "stuck spinlock"  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Список pgsql-hackers
Hi,

On 2013-12-13 15:57:14 -0300, Alvaro Herrera wrote:
> If there was a way for raising an #error at compile time whenever a
> worker relies on the existing signal handler, I would vote for doing
> that.  (But then I have no idea how to do such a thing.)

I don't see a way either given how disconnected registration of the
signal handler is from the bgworker infrastructure. I think the best we
can do is to raise an error in BackgroundWorkerUnblockSignals() - and we
should definitely do that.

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



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

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: "stuck spinlock"
Следующее
От: Andres Freund
Дата:
Сообщение: Re: "stuck spinlock"