Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id B2C562E030A for ; Mon, 7 Jan 2008 11:53:19 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 47462-02 for ; Mon, 7 Jan 2008 11:53:17 -0400 (AST) Received: from mout.perfora.net (mout.perfora.net [74.208.4.197]) by postgresql.org (Postfix) with ESMTP id AAD542E020F for ; Mon, 7 Jan 2008 11:53:16 -0400 (AST) Received: from [172.16.255.106] (66-23-211-34.clients.speedfactory.net [66.23.211.34]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MKp8S-1JBuHo2Fhb-0004Ie; Mon, 07 Jan 2008 10:53:15 -0500 Message-ID: <47824AE7.6000006@serioustechnology.com> Date: Mon, 07 Jan 2008 10:53:11 -0500 From: Geoffrey User-Agent: Thunderbird 1.5.0.8 (X11/20061025) MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: When does VACUUM FULL not clean out all deleted data? References: <10656.1199426607@sss.pgh.pa.us> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX19CNkzDR2xuqw/qNbRmQCkyEa1rmB1aBLXvcf+ RDaXQCUC8iyRPCLCPZKjz0pCsDHrZSnMOVLiuvZDcf8JyFLUKu FuvKM6vvrT4q81A5/JdafqTc8JQMp64 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/76 X-Sequence-Number: 27850 Scott Marlowe wrote: > Note that routine vacuum FULL is not a good idea actually. vacuum > full is something you run when things have gone wrong (i.e. not enough > regular vacuuming) and it is usually best followed by reindexing all > your indexes. > > It's far better to keep track of bloat and run vacuum full, if at all, > by hand, and only when needed. Running it regularly with no > reindexing often results in index bloat which makes the database > slower not faster. I've been trying to research this issue. I can't really find documentation that defines when to 'vacuum full.' That is other then this posting on the list and the following from the man page: 'The FULL option is not recommended for routine use, but may be useful in special cases. An example is when you have deleted most of the rows in a table and would like the table to physically shrink to occupy less disk space. VACUUM FULL will usually shrink the table more than a plain VACUUM would.' So, I'm wondering if anyone can point me to more specific information as to when, if ever, you should 'vacuum full?' The more research I do, the more it appears that you should only 'vacuum full' when you run into space issues. -- Until later, Geoffrey Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. - Benjamin Franklin