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 6E9D7DA5A1 for ; Thu, 10 Nov 2005 11:58:08 -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 57193-06 for ; Thu, 10 Nov 2005 15:58:04 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from outbound.mailhop.org (outbound.mailhop.org [63.208.196.171]) by svr1.postgresql.org (Postfix) with ESMTP id 007A1DA461 for ; Thu, 10 Nov 2005 11:58:06 -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 1EaEoU-0003ST-D8; Thu, 10 Nov 2005 10:58:10 -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: <43736D98.5060205@zeut.net> Date: Thu, 10 Nov 2005 10:56:08 -0500 From: "Matthew T. O'Connor" User-Agent: Thunderbird 1.4 (Windows/20050908) MIME-Version: 1.0 To: Scott Marlowe Cc: Jeff Bohmer , 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> <43727C5E.7090501@zeut.net> <1131635881.3554.60.camel@state.g2switchworks.com> In-Reply-To: <1131635881.3554.60.camel@state.g2switchworks.com> 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/117 X-Sequence-Number: 19490 Scott Marlowe wrote: >> I would appreciate an easy way to keep tabs on autovacuum's activity. >> A stat table seems like a practical way to have this info readily >> available. >> >> No need to keep values across dump/reloads, right? >> > > This sounds more and more like a good idea. I don't think there's any > need to maintain across dump/reload and / or database restart either. The DBA can elect to keep or discard stats data across DB restart, in fact I think the default value for this GUC var was set to true for the 8.1 release. Matt