Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 03F7664FC2F for ; Thu, 6 Nov 2008 07:17:37 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 07505-04 for ; Thu, 6 Nov 2008 07:17:36 -0400 (AST) X-Greylist: delayed 00:20:04.366556 by SQLgrey-1.7.6 Received: from easy2.in-chemnitz.de (easy2.in-chemnitz.de [88.198.17.232]) by mail.postgresql.org (Postfix) with ESMTP id 90DF064FC2D for ; Thu, 6 Nov 2008 07:17:35 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by easy2.in-chemnitz.de (Postfix) with ESMTP id AF1CF4700B6 for ; Thu, 6 Nov 2008 11:57:27 +0100 (CET) Received: from easy2.in-chemnitz.de ([127.0.0.1]) by localhost (easy.in-chemnitz.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lINHIK8JYBXP for ; Thu, 6 Nov 2008 11:57:27 +0100 (CET) Received: by easy2.in-chemnitz.de (Postfix, from userid 1013) id 9EBDD4700B4; Thu, 6 Nov 2008 11:57:27 +0100 (CET) Date: Thu, 6 Nov 2008 11:57:27 +0100 From: Tino Schwarze To: pgsql-admin@postgresql.org Subject: Re: server space increasing very fast but transaction are very low Message-ID: <20081106105727.GC554@easy2.in-chemnitz.de> References: <551154.82667.qm@web8405.mail.in.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <551154.82667.qm@web8405.mail.in.yahoo.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Archive-Number: 200811/40 X-Sequence-Number: 30694 Hi, On Thu, Nov 06, 2008 at 04:15:02PM +0530, brahma tiwari wrote: > My database server db01 is on linux environment and size of base folder increasing very fast unexpectedly(creating renamed files of 1 GB in base folder like 1667234568.10) This sounds like your max_fsm_pages setting is too low, so the server cannot track free pages any more Bump it up (there used to be a rule of thumb, IIRC it was 65536/1 GB of data/disk space - please correct me, if I'm wrong). IIRC, you need to restart PostgresSQL after altering that setting. A VACUUM is prbably a good thing as well, maybe even VACUUM FULL. Do not delete anything! HTH, Tino. -- "What we nourish flourishes." - "Was wir nähren erblüht." www.lichtkreis-chemnitz.de www.craniosacralzentrum.de