Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id A0D0A632A3F for ; Fri, 16 Apr 2010 10:59:20 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 90546-05 for ; Fri, 16 Apr 2010 13:59:01 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10]) by mail.postgresql.org (Postfix) with ESMTP id A8FB26329D3 for ; Fri, 16 Apr 2010 10:59:09 -0300 (ADT) Received: from [192.168.0.105] (pool-96-244-14-10.bltmmd.fios.verizon.net [96.244.14.10]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0LtlMD-1NMBKe0xGP-0114b9; Fri, 16 Apr 2010 15:59:05 +0200 Message-ID: <4BC86D27.4020209@2ndquadrant.com> Date: Fri, 16 Apr 2010 09:59:03 -0400 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Alexandre Leclerc CC: pgsql-admin@postgresql.org Subject: Re: Vacuum Full (PG 8.1) - Urgent help needed - Cancel & transaction "liberation" References: <4BC8639C.4010202@ipso.ca> In-Reply-To: <4BC8639C.4010202@ipso.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1+CA0nKICdHFUH+lqAIVk+GiLk8U8TDDBjJFjY av1aekcXFOspJIeb1+Jf7qozUY8f7S1bqB7j22hko/VZ9yjubj DsxB7swslafaCcs7m7aPX6OpC+zjLeV X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.987 tagged_above=-10 required=5 tests=AWL=-0.087, BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201004/210 X-Sequence-Number: 34304 Alexandre Leclerc wrote: > - 2. Could we stop VACUUM FULL and simply restart postmaster and > starting a normal VACUUM even if it's slow? This is what you want to do. VACUUM FULL is the slow way--much, much slower--and it is not needed to clean up from wraparound issues. Here's two more opinions on that: http://archives.postgresql.org/message-id/5224.1255142294@sss.pgh.pa.us And here's some notes about why you should avoid VACUUM FULL: http://wiki.postgresql.org/wiki/VACUUM_FULL (Note that you don't have a good CLUSTER implementation in your 8.1 server, so using that to clean up tables isn't an option) -- Greg Smith 2ndQuadrant US Baltimore, MD PostgreSQL Training, Services and Support greg@2ndQuadrant.com www.2ndQuadrant.us