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+hUKG+z9NtH8j7JLfX-issbQHUb5vCWw+aEpmxxEZ6=mV-Wjg@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
|
Список | pgsql-hackers |
On Thu, Oct 15, 2020 at 11:18 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: > Thomas Munro <thomas.munro@gmail.com> writes: > > On Thu, Oct 15, 2020 at 8:40 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: > >> 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. > > Oh, OK. I confirm this makes the kqueue path work like the EPOLL and POLL > paths. (I can't test the WIN32 path.) Thanks. Pushed. (Hmm, I wonder about that Windows process exit event.)
В списке pgsql-hackers по дате отправления: