Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 82F616504ED for ; Wed, 26 Nov 2008 15:54:31 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 41152-02-7 for ; Wed, 26 Nov 2008 15:54:26 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from smtp222.iad.emailsrvr.com (smtp222.iad.emailsrvr.com [207.97.245.222]) by mail.postgresql.org (Postfix) with ESMTP id EB46C650521 for ; Wed, 26 Nov 2008 15:54:25 -0400 (AST) Received: from relay12.relay.iad.mlsrvr.com (localhost [127.0.0.1]) by relay12.relay.iad.mlsrvr.com (SMTP Server) with ESMTP id E9AA71FF8B9; Wed, 26 Nov 2008 14:54:21 -0500 (EST) Received: by relay12.relay.iad.mlsrvr.com (Authenticated sender: matthew-AT-zeut.net) with ESMTP id BBB241FF8A9; Wed, 26 Nov 2008 14:54:21 -0500 (EST) Message-ID: <492DA95D.3010303@zeut.net> Date: Wed, 26 Nov 2008 14:54:05 -0500 From: "Matthew T. O'Connor" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8.1.12) Gecko/20080213 Lightning/0.9 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: Rafael Domiciano CC: Scott Marlowe , Rafael Martinez , "pgsql-admin@postgresql.org" Subject: Re: Vacuum Problems References: <3a0028490811260543x74d02719w775a457999cfc74@mail.gmail.com> <492D5C87.5090505@usit.uio.no> <3a0028490811260700w6e8d9d86o24effbe0bea2bddb@mail.gmail.com> <3a0028490811260921l5d6aac06v54dca32aae672b97@mail.gmail.com> In-Reply-To: <3a0028490811260921l5d6aac06v54dca32aae672b97@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200811/156 X-Sequence-Number: 30810 Rafael Domiciano wrote: > I'm not using autovacuum. Regular vacuum goes ok. > To see the last 10 lines of verbose i will need to run vacuum tonight > > If a run a reindex before the vacuum full, increase the "speed" of > doing vacuum? I found something about it googling. It might help a bit, but by the end of VACUUM FULL you would need to run reindex again as VACUUM FULL tends to cause a lot of index bloat. It is normal for tables to have some slack space, so if you do a regular vacuum every day (or let autovacuum) it's normal for the table to be a bit bigger than after a VACUUM FULL, but they should ready steady state and stop growing. You may also want to look into using CLUSTER it will rewrite the whole table and is typically much more efficient that VACUUM FULL, but it requires 2x disk space while running. Matt