Re: kevent latch paths don't handle postmaster death well

Поиск
Список
Период
Сортировка
От Thomas Munro
Тема Re: kevent latch paths don't handle postmaster death well
Дата
Msg-id CA+hUKGJ8aHjyxccsn3z4NOpnWBdfUSmzVPm6uc_B63ODnQvvPA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: kevent latch paths don't handle postmaster death well  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: kevent latch paths don't handle postmaster death well  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: kevent latch paths don't handle postmaster death well  (Andres Freund <andres@anarazel.de>)
Список pgsql-hackers
On Thu, Oct 15, 2020 at 8:40 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Thomas Munro <thomas.munro@gmail.com> writes:
> > The process exit event is like an 'edge', not a 'level'... hmm.  It
> > might be enough to set report_postmaster_not_running = true the first
> > time it tells us so if we try to wait again we'll treat it like a
> > level.  I will look into it later today.
>
> Seems like having that be per-WaitEventSet state is also not a great
> idea --- if we detect PM death while waiting on one WES, and then
> wait on another one, it won't work.  A plain process-wide static
> variable would be a better way I bet.

I don't think that's a problem -- the kernel will report the event to
each interested kqueue object.  The attached fixes the problem for me.

Вложения

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

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: gs_group_1 crashing on 13beta2/s390x
Следующее
От: Tom Lane
Дата:
Сообщение: Re: kevent latch paths don't handle postmaster death well