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 40F30DAC87 for ; Thu, 10 Nov 2005 16:50:29 -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 40794-10 for ; Thu, 10 Nov 2005 20:50:27 +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 7A2A4DA5A1 for ; Thu, 10 Nov 2005 16:50:27 -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.0003133994; Thu, 10 Nov 2005 13:50:26 -0700 Mime-Version: 1.0 Message-Id: In-Reply-To: <4373B07F.5040706@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> <4373B07F.5040706@zeut.net> Date: Thu, 10 Nov 2005 13:50:22 -0700 To: "Matthew T. O'Connor" From: Jeff Bohmer Subject: Re: autovacuum daemon question... Cc: Scott Marlowe , 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.087 required=5 tests=[AWL=0.087] X-Spam-Score: 0.087 X-Spam-Level: X-Archive-Number: 200511/129 X-Sequence-Number: 19502 >>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. > >I'm confused... the GUC var stats_reset_on_server_start dictates if >the stats system dumps its data on DB restart. If we added a new >table to the stats system kept track of autovacuum activity, then >that data would also be dumped on restart if >stats_reset_on_server_start=true. Yep. I was thinking of a way to muck up the stats system by keeping autovacuum's VACUUM activity irregardless of stats_reset_on_server_start. Because autovacuum's VACUUM activity data would be relevant across restarts, even if stats_reset_on_server_start=true. But I see now that my idea is ugly and just confuses things. I agree that having it work the way you suggest is preferable. - Jeff -- Jeff Bohmer VisionLink, Inc.