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 F195FD7BB0 for ; Thu, 10 Nov 2005 12:03:19 -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 59330-09 for ; Thu, 10 Nov 2005 16:03:18 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from koolancexeon.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by svr1.postgresql.org (Postfix) with ESMTP id 3B09FDA4C2 for ; Thu, 10 Nov 2005 12:03:17 -0400 (AST) Received: mail.g2switchworks.com 10.10.1.8 from 10.10.1.37 10.10.1.37 via HTTP with MS-WebStorage 6.5.6944 Received: from state.g2switchworks.com by mail.g2switchworks.com; 10 Nov 2005 10:03:17 -0600 Subject: Re: autovacuum daemon question... From: Scott Marlowe To: "Matthew T. O'Connor" Cc: Jeff Bohmer , Joe Maldonado , pgsql-admin@postgresql.org In-Reply-To: <43736D98.5060205@zeut.net> 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> <43736D98.5060205@zeut.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1131638596.3554.77.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Thu, 10 Nov 2005 10:03:17 -0600 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.007 required=5 tests=[AWL=0.006, UNPARSEABLE_RELAY=0.001] X-Spam-Score: 0.007 X-Spam-Level: X-Archive-Number: 200511/118 X-Sequence-Number: 19491 On Thu, 2005-11-10 at 09:56, Matthew T. O'Connor wrote: > 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. I thought we were discussing a theoretical / not yet in existence GUC var...