Re: Logging pg_autovacuum - Mailing list pgsql-hackers

From Larry Rosenman
Subject Re: Logging pg_autovacuum
Date
Msg-id F6616E0E81AC0841B1F9DD252F7C4B55041A3F@ausmaildd.aus.pervasive.com
Whole thread Raw
In response to Logging pg_autovacuum  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Logging pg_autovacuum
Re: Logging pg_autovacuum
List pgsql-hackers
Larry Rosenman wrote:
> Simon Riggs wrote:
>> On Thu, 2006-04-27 at 14:53 -0400, Tom Lane wrote:
>>> "Larry Rosenman" <lrosenman@pervasive.com> writes:
>>>> I'd like to see a more concrete definition of what we
>>>> want Autovacuum to output and at what levels.
>>>
>>> autovacuum_verbosity
>>
>> Should we call it autovacuum_messages?
>>
>> In current usage...
>>
>> _verbosity controls how much information each message gives
>> _messages controls what types of messages are logged
>
> That probably works, but I'm not sure about the one to add the VERBOSE
> to the
> VACUUM commands autovacuum.c emits.

does the following options satisfy everyone:

autovacuum_messages=
none silent (nothing output at LOG level)
database we'd output a LOG message processing database <name>
table    we'd output a LOG message for each table we actually vacuum /
analyze
verbose  we'd add the verbose flag to each command

the lower levels would include the upper (I.E. verbose implies table +
database).

If this is acceptable, I'm going to start working on the code to
implement it.

LER

--
Larry Rosenman
Database Support Engineer

PERVASIVE SOFTWARE. INC.
12365B RIATA TRACE PKWY
3015
AUSTIN TX  78727-6531

Tel: 512.231.6173
Fax: 512.231.6597
Email: Larry.Rosenman@pervasive.com
Web: www.pervasive.com


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: GIN - Generalized Inverted iNdex. Try 3.
Next
From: Teodor Sigaev
Date:
Subject: Re: GIN - Generalized Inverted iNdex. Try 3.