Re: allowing VACUUM to be cancelled for conflicting locks - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: allowing VACUUM to be cancelled for conflicting locks
Date
Msg-id 20140428155231.GK25695@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: allowing VACUUM to be cancelled for conflicting locks  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: allowing VACUUM to be cancelled for conflicting locks  (Claudio Freire <klaussfreire@gmail.com>)
List pgsql-hackers
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".

As much as I'm a fan of autovacuum, that's not always possible.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Implied BETWEEN from join quals
Next
From: Tom Lane
Date:
Subject: Re: includedir_internal headers are not self-contained