Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 20D719FBD1C for ; Mon, 4 Jun 2007 11:49:26 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 07267-01-7 for ; Mon, 4 Jun 2007 11:49:17 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id 00FED9FBCF8 for ; Mon, 4 Jun 2007 11:49:14 -0300 (ADT) Received: from perhan.alvh.no-ip.org (201-221-217-243.bk12-dsl.surnet.cl [201.221.217.243]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l54En9IH010106; Mon, 4 Jun 2007 07:49:10 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id EFE68329E9; Mon, 4 Jun 2007 10:49:06 -0400 (CLT) Date: Mon, 4 Jun 2007 10:49:06 -0400 From: Alvaro Herrera To: "Charles.Hou" Cc: pgsql-admin@postgresql.org Subject: Re: Auto Vacuum question? Message-ID: <20070604144906.GH4779@alvh.no-ip.org> References: <1180966368.172224.250500@x35g2000prf.googlegroups.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1180966368.172224.250500@x35g2000prf.googlegroups.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: ClamAV version 0.88.5, clamav-milter version 0.88.5 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Mon, 04 Jun 2007 07:49:10 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/17 X-Sequence-Number: 25685 Charles.Hou wrote: > i set the auto vacuum option to enable. but my database size(hard- > disk > space) still increased from 420MB to 440MB in 8 hours. most of the > operations in this database are the "Select" query command, just few > of "Update or Insert". > why it can be increased so strongly? > after i executed the command " vaccumdb -f -z testdb", but the size > just decreased 1 or 2MB... > what's the problem? It is normal that the tables grow a bit to a stationary state of dead space (generated by UPDATE and DELETE). However it is not normal if it loses track of that dead space. One thing you can and should do is adjust the autovacuum settings (for example lowering the vacuum scale factor and threshold values). Another is to correctly set the FSM values. Have you done both? -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.