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 A9810D7BAF for ; Thu, 10 Nov 2005 16:06:44 -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 71549-06 for ; Thu, 10 Nov 2005 20:06:41 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from visionlink.org (unknown [208.139.207.130]) by svr1.postgresql.org (Postfix) with SMTP id 446D6D77CC for ; Thu, 10 Nov 2005 16:06:41 -0400 (AST) Received: from [70.58.29.113] (HELO [192.168.1.200]) by visionlink.org (Stalker SMTP Server 1.8b8) with ESMTP id S.0003133890; Thu, 10 Nov 2005 13:06:41 -0700 Mime-Version: 1.0 Message-Id: In-Reply-To: <4373A1B7.3030005@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> <1131638596.3554.77.camel@state.g2switchworks.com> <4373A1B7.3030005@zeut.net> Date: Thu, 10 Nov 2005 13:06:37 -0700 To: "Matthew T. O'Connor" , Scott Marlowe From: Jeff Bohmer Subject: Re: autovacuum daemon question... Cc: Jeff Bohmer , Joe Maldonado , pgsql-admin@postgresql.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.157 required=5 tests=[AWL=0.157] X-Spam-Score: 0.157 X-Spam-Level: X-Archive-Number: 200511/125 X-Sequence-Number: 19498 >>>>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... > >I assumed (perhaps incorrectly) that you were talking about >maintaining the data in the theoretical / not yet in existence >autovacuum stats table through database restart, the stats system >already has a GUC var that dictates whether or not it dumps it's >data upon DB restart. > >Matt AFAIK, a restart does not affect the VACUUMed-ness of anything. Keeping these (currently nonexistent autovacuum) stats across restarts would be helpful if stats_reset_on_server_start=on. Unless I misunderstand, if stats_reset_on_server_start=off, these (currently nonexistent autovacuum) stats would only be relevant for autovacuum's VACUUM activity and not it's ANALYZE activity. In which case, it seems ideal to keep autovacuum VACUUM stats regardless of the GUC setting, while autovacuum ANALYZE stats should follow it. But if the ideal is impractical, making both ANALYZE and VACUUM stats follow the GUC would still be real nice. - Jeff -- Jeff Bohmer VisionLink, Inc.