Re: "stuck spinlock"

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: "stuck spinlock"
Дата
Msg-id 25316.1386957249@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: "stuck spinlock"  (Andres Freund <andres@2ndquadrant.com>)
Ответы Re: "stuck spinlock"
Список pgsql-hackers
Andres Freund <andres@2ndquadrant.com> writes:
> I wonder what to do about bgworker's bgworker_die()? I don't really see
> how that can be fixed without breaking the API?

IMO it should be flushed and bgworkers should use the same die() handler
as every other backend, or else one like the one in worker_spi, which just
sets a flag for testing later.  If we try to change the signal handling
contracts, 80% of backend code will be unusable in bgworkers, which is not
where we want to be I think.
        regards, tom lane



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

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