Re: More logging for autovacuum

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Decibel! wrote:
> On Tue, Aug 07, 2007 at 11:59:03AM -0700, Andrew Hammond wrote:
>> On 8/7/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> Peter Eisentraut <peter_e(at)gmx(dot)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.
>
> Is logging really the answer for that? ISTM it'd be better to provide
> statistics info so that you could monitor autovacuum activity with
> things like cricket, SNMP, etc.

Well that would certainly be useful too.

Joshua D. Drake

- --

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGuOZBATb/zqfZUUQRAmy6AKCohv/RtFmPCA+zmmpkwR1qCX3XugCgg/rE
lq3wxodgiWNe0d1wmw1ragc=
=X6W3
-----END PGP SIGNATURE-----