Re: More logging for autovacuum - Mailing list pgsql-hackers

From Andrew Hammond
Subject Re: More logging for autovacuum
Date
Msg-id 5a0a9d6f0708071159g5e6c73eet98d5a4aee1289414@mail.gmail.com
Whole thread Raw
In response to Re: More logging for autovacuum  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: More logging for autovacuum  (Decibel! <decibel@decibel.org>)
List pgsql-hackers
On 8/7/07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Peter Eisentraut <peter_e@gmx.net> writes:
> But INFO is not shown by default.

INFO is mostly a hack to try to emulate VACUUM VERBOSE's ancient
behavior before we redesigned the elog levels.  It's intended for
controlling messages that should go to a client because the client
asked for them, and usually should NOT go to the log.  I think it's
100% inappropriate to use it for messages from a background process
that has no client.

Traditional log-level semantics aren't very rich. I think that's the real source of this problem: "How do I get the info I need to tune auto-vacuum without swamping my system with log IO". While the following isn't production ready, it seems to have some really good ideas.

http://log4c.sourceforge.net/

log4c is inspired by log4j, which seems to have become the defacto standard tool for logging in the enterprise java world.

Andrew

pgsql-hackers by date:

Previous
From: Arthernan
Date:
Subject: Internal Postgre SQL documentation
Next
From: "Simon Riggs"
Date:
Subject: Re: HOT patch, missing things