Re: Autovacuum worker doesn't immediately exit on postmaster death

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: Autovacuum worker doesn't immediately exit on postmaster death
Дата
Msg-id CA+TgmobzFa1LOcGJo2nzr8mdZJCj=GndtcJZn9t4hhQ3YPr24A@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Autovacuum worker doesn't immediately exit on postmaster death  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Ответы Re: Autovacuum worker doesn't immediately exit on postmaster death  (Thomas Munro <thomas.munro@gmail.com>)
Список pgsql-hackers
On Thu, Oct 29, 2020 at 5:36 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> Maybe instead of thinking specifically in terms of vacuum, we could
> count buffer accesses (read from kernel) and check the latch once every
> 1000th such, or something like that.  Then a very long query doesn't
> have to wait until it's run to completion.  The cost is one integer
> addition per syscall, which should be bearable.

Interesting idea. One related case is where everything is fine on the
server side but the client has disconnected and we don't notice that
the socket has changed state until something makes us try to send a
message to the client, which might be a really long time if the
server's doing like a lengthy computation before generating any rows.
It would be really nice if we could find a cheap way to check for both
postmaster death and client disconnect every now and then, like if a
single system call could somehow answer both questions.

-- 
Robert Haas
EDB: http://www.enterprisedb.com



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

Предыдущее
От: John Naylor
Дата:
Сообщение: Re: cutting down the TODO list thread
Следующее
От: Tomas Vondra
Дата:
Сообщение: extended statistics - functional dependencies vs. MCV lists