Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id A8BC09FBADB for ; Thu, 24 May 2007 13:09:08 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 45146-03 for ; Thu, 24 May 2007 13:09:04 -0300 (ADT) X-Greylist: delayed 00:15:43.509358 by SQLgrey-1.7.5 Received: from srvftpmail.saga.it (host89-166-static.47-88-b.business.telecomitalia.it [88.47.166.89]) by postgresql.org (Postfix) with ESMTP id 96DA89FBA3F for ; Thu, 24 May 2007 13:09:04 -0300 (ADT) Received: from [10.77.1.25] ([10.77.1.25]) by srvmailbs.bs.local (Lotus Domino Release 6.5.2) with ESMTP id 2007052417560935-8392 ; Thu, 24 May 2007 17:56:09 +0200 Message-ID: <4655B59A.7080409@saga.it> Date: Thu, 24 May 2007 17:56:10 +0200 From: Nicola Mauri User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Abnormal storage consumption with autovacuum enabled X-MIMETrack: Itemize by SMTP Server on saga_bs1/saga(Release 6.5.2|June 01, 2004) at 24/05/2007 17.56.09, Serialize by Router on Front_Bs/saga at 05/24/2007 06:10:54 PM, Serialize complete at 05/24/2007 06:10:54 PM X-NAI-Spam-Flag: NO X-NAI-Spam-Score: -2.500 X-NAI-Spam-Threshold: 5.000 X-NAI-Spam-Rules: 1 rules triggered BAYES_00=-2.500 X-NAI-Checker-Version: NAI SpamAssassin 1.2 (2.70 20070523 2766) Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=ISO-8859-15; format=flowed X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/272 X-Sequence-Number: 25592 I'm using 8.1.4 on linux. Autovacuum is enable with these settings: stats_start_collector = on stats_row_level = on autovacuum = on autovacuum_naptime = 60 autovacuum_vacuum_threshold = 1000 autovacuum_analyze_threshold = 500 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? I'm quite sure that data in tables never reached that size, during normal operations. Could be autovacuum not working properly? How to diagnose or make sure that autovacuum is doing its job? Thanks in advance! Nicola