X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 79B16D1B4F4 for ; Mon, 13 Oct 2003 09:26:16 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 65662-03 for ; Mon, 13 Oct 2003 06:25:28 -0300 (ADT) Received: from smtp.pspl.co.in (unknown [202.54.11.65]) by svr1.postgresql.org (Postfix) with ESMTP id 48489D1B505 for ; Mon, 13 Oct 2003 06:25:24 -0300 (ADT) Received: (from root@localhost) by smtp.pspl.co.in (8.12.9/8.12.9) id h9D9Vawp028981 for ; Mon, 13 Oct 2003 15:01:36 +0530 Received: from persistent.co.in (daithan.intranet.pspl.co.in [192.168.7.161]) (authenticated bits=0) by persistent.co.in (8.12.9/8.12.9) with ESMTP id h9D9VZwc028955; Mon, 13 Oct 2003 15:01:35 +0530 Message-ID: <3F8A6F82.6030300@persistent.co.in> Date: Mon, 13 Oct 2003 14:55:22 +0530 From: Shridhar Daithankar Organization: Persistent Systems Pvt. Ltd. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030917 Thunderbird/0.3a X-Accept-Language: en-us, en MIME-Version: 1.0 To: Seum-Lim Gan Cc: pgsql-performance@postgresql.org Subject: Re: Performance, vacuum and reclaiming space, fsm References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/416 X-Sequence-Number: 4164 Seum-Lim Gan wrote: > I have a table that keeps being updated and noticed > that after a few days, the disk usage has growned to > from just over 150 MB to like 2 GB ! Hmm... You have quite a lot of wasted space there.. > > I followed the recommendations from the various search > of the archives, changed the max_fsm_relations, pages, > keep doing vacuum like every minute while the > table of interest in being updated. I kept > watching the disk space usage and still noticed that > it continues to increase. That will help if your table is in good shape. Otherwise it will have little effect particularly after such amount of wasted space. > Looks like vacuum has no effect. Its not that. > I did vacuum tablename and don't intend to use > the full option since it locks the table. You got to do that. simple vacuum keeps a running instance of server clean. But once dead tuples spill to disk, nothing but vacumm full can reclaim that space. And don't forget, you got to reindex the indexes as well. Once your table is in good shape, you can tune max_fsm_* and vacuum once a minute. That will keep it good.. > I have 7.3.3 running in Solaris 9. > > Any recommendation ? HTH Shridhar