Re: We need to log aborted autovacuums

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Greg Smith <greg(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: We need to log aborted autovacuums
Date: 2011-02-04 12:08:58
Message-ID: AANLkTin5eUjs+Mv-EV3ZBhHkQhK0CMxvhsxaKQPLj3Nv@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Feb 4, 2011 at 12:59 AM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> Robert,
>
>> Seeing as how there seem to be neither objections nor endorsements,
>> I'm inclined to commit what I proposed more or less as-is.  There
>> remains the issue of what do about the log spam.  Josh Berkus
>> suggested logging it when log_autovacuum_min_duration != -1, which
>> seems like a bit of an abuse of that setting, but it's certainly not
>> worth adding another setting for, and the alternative of logging it
>> at, say, DEBUG2 seems unappealing because you'll then have to turn on
>> logging for a lot of unrelated crap to get this information.  So on
>> balance I think that proposal is perhaps the least of evils.
>
> Wait, which proposal is?

I meant to say that I think the "least evil" proposal is to log at LOG
when log_autovacuum_min_duration != -1.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thom Brown 2011-02-04 12:32:33 Re: Issues with generate_series using integer boundaries
Previous Message Robert Haas 2011-02-04 12:07:20 Re: Compilation failed