X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id C22E4DA7AB for ; Wed, 9 Nov 2005 17:26:36 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 98001-01 for ; Wed, 9 Nov 2005 21:26:30 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 4DE8ADB1C5 for ; Wed, 9 Nov 2005 17:25:56 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id jA9LPu6i019440; Wed, 9 Nov 2005 16:25:56 -0500 (EST) To: Joe Maldonado Cc: "Matthew T. O'Connor" , pgsql-admin@postgresql.org Subject: Re: autovacuum daemon question... In-reply-to: <824355640511091134t7123bb51sf759391f68c1590f@mail.gmail.com> References: <824355640511090720l27eabde8r61573e574f4904ab@mail.gmail.com> <437227FA.9020502@tocr.com> <824355640511091134t7123bb51sf759391f68c1590f@mail.gmail.com> Comments: In-reply-to Joe Maldonado message dated "Wed, 09 Nov 2005 14:34:51 -0500" Date: Wed, 09 Nov 2005 16:25:56 -0500 Message-ID: <19439.1131571556@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.006 required=5 tests=[AWL=0.006] X-Spam-Score: 0.006 X-Spam-Level: X-Archive-Number: 200511/106 X-Sequence-Number: 19479 Joe Maldonado writes: > I agree...for now while I'm developing and debugging my application I can > have the logging be that verbose...I agree that these should be handled as > info messages, since they are invaluable in investigating problems. This would be a pretty bad idea IMHO, since it would lead to bloating the logs with autovacuum progress messages by default --- and whatever you may think about it, I really doubt that the average DBA will want those messages there all the time. I wonder whether it would be practical to let the autovacuum daemon have its own value of log_min_messages. The alternative to that seems to be to invent a new log severity level just for autovacuum, which is pretty gross (especially since it's not obvious how it should sort relative to LOG and DEBUG1). regards, tom lane