X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 0EB2D535E3 for ; Mon, 18 Apr 2005 14:32:56 -0300 (ADT) 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 05760-08 for ; Mon, 18 Apr 2005 17:32:54 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id C67E8535E2 for ; Mon, 18 Apr 2005 14:32:48 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j3IHWmix023920; Mon, 18 Apr 2005 13:32:48 -0400 (EDT) To: "Rodrigo Moreno" Cc: pgsql-performance@postgresql.org Subject: Re: RES: How to improve postgres performace In-reply-to: <20050418163126.E004E14C097@talara.terra.com.br> References: <20050418163126.E004E14C097@talara.terra.com.br> Comments: In-reply-to "Rodrigo Moreno" message dated "Mon, 18 Apr 2005 13:31:22 -0300" Date: Mon, 18 Apr 2005 13:32:48 -0400 Message-ID: <23919.1113845568@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200504/412 X-Sequence-Number: 11809 "Rodrigo Moreno" writes: > The current values for: > max_fsm_pages = 1048576 > max_fsm_relations = 1000 > this is enough ? That max_fsm_pages value is enough to cover 8Gb, so it should work OK for a database disk footprint up to 10 or so Gb. I don't know how many tables in your installation so I can't say if max_fsm_relations is high enough, but you can check that by looking at the tail end of the output of VACUUM VERBOSE. (Or just count 'em ;-)) Offhand these look reasonable, though, so if you are seeing database bloat over time it probably means you need to tweak your autovacuum settings. I'm not much of an autovacuum expert, but maybe someone else can help you there. You might want to keep track of physical file sizes over a period of time and try to determine exactly where the bloat is happening. regards, tom lane