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 1BA29DAF90 for ; Thu, 10 Nov 2005 16:43:39 -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 40905-04 for ; Thu, 10 Nov 2005 20:43:36 +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 BB397DAFCC for ; Thu, 10 Nov 2005 16:43:37 -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 1EaJGj-000Gxf-Ex; Thu, 10 Nov 2005 15:43:37 -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: <4373B07F.5040706@zeut.net> Date: Thu, 10 Nov 2005 15:41:35 -0500 From: "Matthew T. O'Connor" User-Agent: Thunderbird 1.4 (Windows/20050908) MIME-Version: 1.0 To: Jeff Bohmer Cc: Scott Marlowe , 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> <43736D98.5060205@zeut.net> <1131638596.3554.77.camel@state.g2switchworks.com> <4373A1B7.3030005@zeut.net> In-Reply-To: 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/128 X-Sequence-Number: 19501 Jeff Bohmer wrote: >> 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. > 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. 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.