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 A74D853C91 for ; Fri, 18 Mar 2005 00:37:17 +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 37370-03 for ; Fri, 18 Mar 2005 00:37:14 +0000 (GMT) Received: from polaris.pinpointresearch.com (66-7-238-130.cust.telepacific.net [66.7.238.130]) by svr1.postgresql.org (Postfix) with ESMTP id 921DD56581 for ; Fri, 18 Mar 2005 00:37:13 +0000 (GMT) Received: from betelgeuse.pinpointresearch.com (betelgeuse.pinpointresearch.com [192.168.1.179]) by polaris.pinpointresearch.com (Postfix) with ESMTP id 4F48F1038E for ; Thu, 17 Mar 2005 16:37:17 -0800 (PST) From: Steve Crawford Organization: Pinpoint Research To: pgsql-admin@postgresql.org Subject: Re: Excessive growth of pg_attribute and other system tables Date: Thu, 17 Mar 2005 16:37:16 -0800 User-Agent: KMail/1.5.1 References: <200503171515.38214.scrawford@pinpointresearch.com> <28709.1111103484@sss.pgh.pa.us> In-Reply-To: <28709.1111103484@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200503171637.16975.scrawford@pinpointresearch.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.095 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200503/281 X-Sequence-Number: 16779 On Thursday 17 March 2005 3:51 pm, Tom Lane wrote: > Steve Crawford writes: > > My autovacuum config is running and I do see regular periodic > > vacuums of these pg_ tables but still they grow. > > Do you have the FSM settings set large enough to account for all > the free space? max_fsm_pages = 20000 max_fsm_relations = 1000 I just poked through the cluster. I have 6 user databases plus template0 and template1. Total tables in the cluster has reached slightly over 1,000 user tables plus all the system tables in the 8 databases. Does this indicate that I need to increase max_fsm_relations to greater than the total number of tables in the cluster? If so it's not a problem as bumping it to 2000 will only cost me ~50k of my 4G memory plus a bit more since max_fsm_pages would have to be increased to at least 32000. > Also you might want to check for newer versions of autovacuum. I > recall that the earlier releases had bugs that sometimes made it > skip vacuuming tables that should be vacuumed. 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? Cheers, Steve