Re: allowing VACUUM to be cancelled for conflicting locks

On 2014-04-28 09:54:49 -0400, Tom Lane wrote:
> 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".

E.g. manually scheduling the full table vacuums to happen during low
activity periods is a very good idea on busy servers.

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services