Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: allowing VACUUM to be cancelled for conflicting locks
Date
Msg-id 9436.1398693289@sss.pgh.pa.us
Whole thread Raw
In response to allowing VACUUM to be cancelled for conflicting locks  (Abhijit Menon-Sen <ams@2ndquadrant.com>)
Responses 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>)
List pgsql-hackers
Tree view 
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 by date:

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