Re: Excessive PostmasterIsAlive calls slow down WAL redo
| От | Andres Freund |
|---|---|
| Тема | Re: Excessive PostmasterIsAlive calls slow down WAL redo |
| Дата | |
| Msg-id | E5042BE5-F72C-4DB5-A15F-DDBBB93BCD3E@anarazel.de обсуждение исходный текст |
| Ответ на | Re: Excessive PostmasterIsAlive calls slow down WAL redo (Alvaro Herrera <alvherre@alvh.no-ip.org>) |
| Ответы |
Re: Excessive PostmasterIsAlive calls slow down WAL redo
|
| Список | pgsql-hackers |
On April 9, 2018 6:31:07 PM PDT, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: >Andres Freund wrote: > >> Another approach, that's simpler to implement, is to simply have a >> second selfpipe, just for WL_POSTMASTER_DEATH. > >Would it work to use this second pipe, to which each child writes a >byte >that postmaster never reads, and then rely on SIGPIPE when postmaster >dies? Then we never need to do a syscall. I'm not following, could you expand on what you're suggesting? Note that you do not get SIGPIPE for already buffered writes. Which syscall can we avoid? Andres -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
В списке pgsql-hackers по дате отправления: