| From: | Andres Freund <andres(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 17:51:06 |
| Message-ID: | 20140428175106.GD14464@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2014-04-28 09:54:49 -0400, 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".
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-04-28 17:58:10 | Re: allowing VACUUM to be cancelled for conflicting locks |
| Previous Message | Claudio Freire | 2014-04-28 17:48:13 | Re: allowing VACUUM to be cancelled for conflicting locks |