From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Cancelling of autovacuums considered harmful |
Date: | 2014-02-26 21:34:33 |
Message-ID: | CAOR=d=2u3UL031Ui7SHUXDwn4HCaTGQ1goFzRez1xGhy17KapA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Feb 26, 2014 at 9:56 AM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Scott Marlowe escribió:
>> As some of you folks know I work on some pretty beefy machines. Some
>> of these machines don't see rest for months or days on end. And
>> autovacuum keeps cancelling. I set it more aggressive, it still never
>> finishes.
>
> No matter how heavily updated, regular activity should not cause
> autovacuum kills. Only heavier operations would do that (say ALTER
> TABLE, etc).
Is there any logging of what killed the autovac available? I've looked
and not seen anything (currently on 8.4 moving to 9.2 soon.)
>> We've now had to schedule manual vacuums because autovac never
>> finishes on large heavily updated tables.
>
>> Is there some way to turn off the cancelling of autovacuums?
>
> I don't think we have a setting for that.
Well it looks like it's slony 1.2 doing it. I'm gonna turn off autovac
on the slony tables and see if it stops.
From | Date | Subject | |
---|---|---|---|
Next Message | john gale | 2014-02-26 21:57:24 | Re: cannot delete corrupted rows after DB corruption: tuple concurrently updated |
Previous Message | Jeff Janes | 2014-02-26 21:27:16 | Re: Cancelling of autovacuums considered harmful |