Re: allowing VACUUM to be cancelled for conflicting locks

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: allowing VACUUM to be cancelled for conflicting locks
Дата
Msg-id 9436.1398693289@sss.pgh.pa.us
обсуждение исходный текст
Ответ на allowing VACUUM to be cancelled for conflicting locks  (Abhijit Menon-Sen <ams@2ndquadrant.com>)
Ответы Re: allowing VACUUM to be cancelled for conflicting locks  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: allowing VACUUM to be cancelled for conflicting locks  (Andres Freund <andres@2ndquadrant.com>)
Re: allowing VACUUM to be cancelled for conflicting locks  (Jeff Janes <jeff.janes@gmail.com>)
Список pgsql-hackers
Abhijit Menon-Sen <ams@2ndquadrant.com> writes:
> In the past, we've had situations where "everything is hung" turned out
> to be because of a script that ran manual VACUUM that was holding some
> lock. It's admittedly not a huge problem, but it might be useful if a
> manual VACUUM could be cancelled the way autovacuum can be.

I think the real answer to that is "stop using manual VACUUM".
        regards, tom lane



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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: includedir_internal headers are not self-contained
Следующее
От: Robert Haas
Дата:
Сообщение: Re: Implied BETWEEN from join quals