X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 46BD09DCA6F for ; Thu, 23 Feb 2006 19:44:52 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 94910-07 for ; Thu, 23 Feb 2006 19:44:54 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from astro.systems.pipex.net (astro.systems.pipex.net [62.241.163.6]) by postgresql.org (Postfix) with ESMTP id 1C1A79DCA7F for ; Thu, 23 Feb 2006 19:44:48 -0400 (AST) Received: from flange.edesix.com (81-86-64-236.dsl.pipex.com [81.86.64.236]) by astro.systems.pipex.net (Postfix) with ESMTP id 43710E000201 for ; Thu, 23 Feb 2006 23:44:48 +0000 (GMT) Received: from host86-131-248-27.range86-131.btcentralplus.com ([86.131.248.27] helo=[192.168.101.208]) by flange.edesix.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.50) id 1FCQ8e-0005W6-0I for pgsql-admin@postgresql.org; Thu, 23 Feb 2006 23:44:48 +0000 Message-ID: <43FE48EF.4000409@edesix.com> Date: Thu, 23 Feb 2006 23:44:47 +0000 From: Robin Iddon User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: 8.0.3 pg_autovacuum doesn't clear out stats table? References: <43FD7312.5080701@edesix.com> <43FDF046.2050609@zeut.net> <43FDFF9A.90603@edesix.com> <43FE0723.3070608@edesix.com> <26139.1140730764@sss.pgh.pa.us> <43FE467E.9090204@edesix.com> In-Reply-To: <43FE467E.9090204@edesix.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.12 required=5 tests=[AWL=0.120] X-Spam-Score: 0.12 X-Spam-Level: X-Archive-Number: 200602/302 X-Sequence-Number: 20723 > > In fact I just noticed that the number of stats tuples just climbed > from 1236 to 2634. The ins/del counts are still zero. I ran analyze > and the update counter went up only by 1232. For pg_autovacuum to > vacuum this table I need (2*2634)+1000 = 6268 updates, which is never > going to happen. At least not before the number of tuples has climbed to beyond that count based on my experience to date! Robin