Re: allowing VACUUM to be cancelled for conflicting locks

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: allowing VACUUM to be cancelled for conflicting locks
Date: 2014-04-28 15:52:31
Message-ID: 20140428155231.GK25695@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Abhijit Menon-Sen <ams(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-04-28 16:14:30 Re: includedir_internal headers are not self-contained
Previous Message Simon Riggs 2014-04-28 15:52:01 Re: Implied BETWEEN from join quals