Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 5E1B29FBEED for ; Thu, 24 May 2007 13:40:15 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 99830-03 for ; Thu, 24 May 2007 13:40:06 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 0FCA89FB89E for ; Thu, 24 May 2007 13:40:06 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l4OGe6mG006033; Thu, 24 May 2007 12:40:06 -0400 (EDT) To: Nicola Mauri cc: pgsql-admin@postgresql.org Subject: Re: Abnormal storage consumption with autovacuum enabled In-reply-to: <4655B59A.7080409@saga.it> References: <4655B59A.7080409@saga.it> Comments: In-reply-to Nicola Mauri message dated "Thu, 24 May 2007 17:56:10 +0200" Date: Thu, 24 May 2007 12:40:06 -0400 Message-ID: <6032.1180024806@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/275 X-Sequence-Number: 25595 Nicola Mauri writes: > Data stored in the database didn't groove very much in the last months > (pg_dump still generates a 4GB compressed file), but data files now > occupies 20 GB on disk. > I know that a vacuum full or a full dump/restore is needed to reclaim > filesystem space. However, my question is: how this could have been > happened? What do you have max_fsm_pages set to? If it's too small, you'll get bloat regardless of whether autovac is doing its thing. regards, tom lane