| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Cancelling of autovacuums considered harmful |
| Date: | 2014-02-26 22:08:57 |
| Message-ID: | CAMkU=1x02mg41x6hE8pZ38VLt3BFyDsM749zjpVhHuTFtd0Pgw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Feb 26, 2014 at 1:34 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>wrote:
> 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.)
>
Better logging for that was introduced in 8.4.13 and 9.2.0.
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Crawford | 2014-02-27 00:40:51 | Re: Cancelling of autovacuums considered harmful |
| Previous Message | john gale | 2014-02-26 21:57:24 | Re: cannot delete corrupted rows after DB corruption: tuple concurrently updated |