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 7BF34D9DB3 for ; Wed, 9 Nov 2005 18:48:58 -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 23405-01 for ; Wed, 9 Nov 2005 22:48:55 +0000 (GMT) X-Greylist: delayed 05:59:24.216929 by SQLgrey- Received: from outbound.mailhop.org (outbound.mailhop.org [63.208.196.171]) by svr1.postgresql.org (Postfix) with ESMTP id CE50ED9AE8 for ; Wed, 9 Nov 2005 18:48:55 -0400 (AST) Received: from ool-4350c7ad.dyn.optonline.net ([67.80.199.173] helo=[192.168.0.91]) by outbound.mailhop.org with esmtpa (Exim 4.51) id 1EZykT-000MES-44; Wed, 09 Nov 2005 17:48:57 -0500 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 67.80.199.173 X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: zeut Message-ID: <43727C5E.7090501@zeut.net> Date: Wed, 09 Nov 2005 17:46:54 -0500 From: "Matthew T. O'Connor" User-Agent: Thunderbird 1.4 (Windows/20050908) MIME-Version: 1.0 To: Tom Lane Cc: Joe Maldonado , pgsql-admin@postgresql.org Subject: Re: autovacuum daemon question... References: <824355640511090720l27eabde8r61573e574f4904ab@mail.gmail.com> <437227FA.9020502@tocr.com> <824355640511091134t7123bb51sf759391f68c1590f@mail.gmail.com> <19439.1131571556@sss.pgh.pa.us> In-Reply-To: <19439.1131571556@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.003 required=5 tests=[AWL=0.003] X-Spam-Score: 0.003 X-Spam-Level: X-Archive-Number: 200511/110 X-Sequence-Number: 19483 Tom Lane wrote: > 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). While I personally think this would probably be a good idea, I also recognize that it might be a solution in search of a problem. Now that we have integrated autovacuum we should probably wait and see what feedback we get from the field. That said, my argument for more detailed logging of autovacuum activity is that vacuuming is VERY important part of proper PG maintenance, as such lots of admins like to keep a proactive eye to make sure there tables are getting the maintenance they need. Another thought: How about adding something to the stats system that an admin can turn on / off. Maybe anew relation called pg_stat_autovacuum_activity this would detail the last vacuum, last analyze, number of vacuums / analyzes in the last 24 hours, last month etc... I dunno, whatever peopel think is relevant. Thoughts? Matt