Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 7AE089FBF8D for ; Tue, 15 May 2007 22:13:08 -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 19961-10 for ; Tue, 15 May 2007 22:12:59 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id 7DF419FBC5A for ; Tue, 15 May 2007 22:12:59 -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 l4G1CvlE030040; Tue, 15 May 2007 18:12:58 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 6276432A13; Tue, 15 May 2007 21:12:52 -0400 (CLT) Date: Tue, 15 May 2007 21:12:52 -0400 From: Alvaro Herrera To: Nick Urbanik Cc: pgsql-admin@postgresql.org Subject: Re: How overcome wait for vacuum full? Message-ID: <20070516011252.GW12731@alvh.no-ip.org> References: <20070515221356.GG5264@nicku.org> <20070515225313.GV12731@alvh.no-ip.org> <20070515231616.GH5264@nicku.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070515231616.GH5264@nicku.org> 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]); Tue, 15 May 2007 18:12:59 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/132 X-Sequence-Number: 25452 Nick Urbanik wrote: > Thank you Alvaro, > > On 15/05/07 18:53 -0400, Alvaro Herrera wrote: > >Instead of waiting a month for the time when you can take the > >application offline (thus accumulating a month's worth of dead tuples), > >run a non-full vacuum more often (say, once a day or more). It doesn't > >lock the table so the app can continue to be online while it runs. > > Yes, it is vacuumed non-full regularly. However, for some reason, > only a full vacuum will recover the space. You probably need to better configure the FSM settings. See fsm_max_pages in the docs. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.