Re: Signals in a BGW

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: Signals in a BGW
Дата
Msg-id 20171207195801.wugc5wcyarblwhp6@alap3.anarazel.de
обсуждение исходный текст
Ответ на Re: Signals in a BGW  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: Signals in a BGW  (Chapman Flack <chap@anastigmatix.net>)
Список pgsql-hackers
On 2017-12-07 12:35:07 -0500, Robert Haas wrote:
> On Wed, Dec 6, 2017 at 6:59 PM, Chapman Flack <chap@anastigmatix.net> wrote:
> >> The default handler is bgworker_die ; see src/backend/postmaster
> >> /bgworker.c
> >> . I don't know if elog() is safe in a signal handler, but I guess in
> >> the absence of non-reentrant errcontext functions...
> >
> > That does seem bold, doesn't it?
> 
> Yes, I think it's flat busted.

We've had that discussion a couple times. The concensus so far has been
that FATALing is considered kinda ok, everything else not. But it
definitely has caused issues in the ast, mostly due to malloc being
entered while already in malloc.

Greetings,

Andres Freund


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

Предыдущее
От: Chapman Flack
Дата:
Сообщение: Re: Logical replication without a Primary Key
Следующее
От: Andres Freund
Дата:
Сообщение: Re: Postgres with pthread