| From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com>, PostgreSQL-Dev <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: allowing VACUUM to be cancelled for conflicting locks |
| Date: | 2014-04-28 17:48:13 |
| Message-ID: | CAGTBQpZP-+qz2ZMjWqarNSr541-53ywj_ORQB4BzSmqRTKgLrw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Apr 28, 2014 at 12:52 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> 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.
Or even recommended, unless the docs changed radically in the last
couple of weeks.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-04-28 17:51:06 | Re: allowing VACUUM to be cancelled for conflicting locks |
| Previous Message | Tom Lane | 2014-04-28 17:25:56 | Re: Different behaviour of concate() and concate operator || |