Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id F09CAB5DC33 for ; Fri, 15 Jul 2011 16:18:04 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 82774-08 for ; Fri, 15 Jul 2011 19:17:59 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from gw.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by mail.postgresql.org (Postfix) with ESMTP id 9943BB5DC1E for ; Fri, 15 Jul 2011 16:17:58 -0300 (ADT) Received: from Courts-MTA by gw.wicourts.gov with Novell_GroupWise; Fri, 15 Jul 2011 14:17:58 -0500 Message-Id: <4E204C0B020000250003F3AB@gw.wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 8.0.1 Date: Fri, 15 Jul 2011 14:17:47 -0500 From: "Kevin Grittner" To: "Simon Riggs" , "David Ondrejik" , "pgsql-admin" , "Tom Lane" Subject: Re: vacuumdb question/problem References: <4E206658.4040600@noaa.gov> <3239.1310749967@sss.pgh.pa.us> <4E208B57.6010401@noaa.gov> In-Reply-To: <4E208B57.6010401@noaa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.899 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RP_MATCHES_RCVD=0.001 X-Spam-Level: X-Archive-Number: 201107/118 X-Sequence-Number: 37897 David Ondrejik wrote: > So I had to kill my process, recover disk space and get the > machine back in working condition for the weekend. I guess I will > attempt to do the full vacuum again next week. Why do you think that you need a VACUUM FULL? That is only needed as an extreme measure in rather unusual circumstances. We run hundreds of PostgreSQL databases, and have not used VACUUM FULL for years. On the other hand, we VACUUM ANALYZE most databases in their entirety every night. (Be very careful not to confuse VACUUM FULL with vacuum of an entire database.) On the other hand, the failed attempt at VACUUM FULL may have bloated your indexes, so you might want to REINDEX the table next week, followed by a VACUUM ANALYZE (without the FULL). -Kevin