X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 6A77E56698 for ; Mon, 21 Mar 2005 19:07:12 +0000 (GMT) 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 12629-03 for ; Mon, 21 Mar 2005 19:07:08 +0000 (GMT) Received: from outbound.mailhop.org (outbound.mailhop.org [63.208.196.171]) by svr1.postgresql.org (Postfix) with ESMTP id B4034566AA for ; Mon, 21 Mar 2005 19:07:08 +0000 (GMT) Received: from ool-4350c7ad.dyn.optonline.net ([67.80.199.173] helo=[192.168.0.66]) by outbound.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.44) id 1DDSF1-000FzL-9V; Mon, 21 Mar 2005 14:07:07 -0500 Message-ID: <423F1B4E.5070507@zeut.net> Date: Mon, 21 Mar 2005 14:06:54 -0500 From: "Matthew T. O'Connor" Organization: Terrie O'Connor Realtors User-Agent: Mozilla Thunderbird 1.0RC1 (Windows/20041201) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: Steve Crawford , pgsql-admin@postgresql.org Subject: Re: Excessive growth of pg_attribute and other system tables References: <200503171515.38214.scrawford@pinpointresearch.com> <28709.1111103484@sss.pgh.pa.us> <200503171637.16975.scrawford@pinpointresearch.com> <29316.1111109568@sss.pgh.pa.us> In-Reply-To: <29316.1111109568@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mail-Handler: MailHop Outbound by DynDNS.org X-Originating-IP: 67.80.199.173 X-Report-Abuse-To: abuse@dyndns.org (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: zeut X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.009 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/330 X-Sequence-Number: 16828 Tom Lane wrote: >Steve Crawford writes: > > >>pg_autovacuum is from 7.4.6 release and is showing periodic vacuums of >>the problem tables. I thought that bug was in some release prior to >>7.4.6. Does the bug allow it to show a vacuum taking place but not do >>it? >> >> > >I don't recall the details of the changes; you could look at the CVS >logs to see what got fixed when. But in any case I think we see the >main problem: max_fsm_pages too small. > > The relevant pg_autovacuum bugs where fixed prior to 7.4.6