Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 59C9A6326F5 for ; Fri, 16 Apr 2010 16:44:58 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 33760-01 for ; Fri, 16 Apr 2010 19:44:47 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.9]) by mail.postgresql.org (Postfix) with ESMTP id 92B45632A6A for ; Fri, 16 Apr 2010 16:44:47 -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=mreu2) with ESMTP (Nemesis) id 0LgcCX-1Ni2u91trB-00oY0g; Fri, 16 Apr 2010 21:44:37 +0200 Message-ID: <4BC8BE22.5030201@2ndquadrant.com> Date: Fri, 16 Apr 2010 15:44:34 -0400 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Kevin Grittner CC: jd@commandprompt.com, Alexandre Leclerc , pgsql-admin@postgresql.org Subject: Re: Vacuum Full (PG 8.1) - Urgent help needed - Cancel & transaction "liberation" References: <4BC8639C.4010202@ipso.ca> <9048.1271429162@sss.pgh.pa.us> <4BC8A623.8090201@ipso.ca> <4BC8638E0200002500030A01@gw.wicourts.gov> <4BC8B0CE.2010401@ipso.ca> <1271444725.21263.80.camel@jd-desktop.unknown.charter.com> <4BC871F90200002500030A0D@gw.wicourts.gov> In-Reply-To: <4BC871F90200002500030A0D@gw.wicourts.gov> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX19RPDeZXalxGlCt0Mfe0vFJq6DsiHBrpet5aXI 2dHQJQXN+qjPhCiOmueFBN+Ik42gkCDOSXsaT1/LeSRhFIH2ax R/lNYQgqrYbZYpP6xE8TgesH1OLFfaA X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201004/229 X-Sequence-Number: 34323 Kevin Grittner wrote: > Also, the "full-database vacuum" terminology seems too likely to be > interpreted as VACUUM FULL for best results. Perhaps it's worth > changing that to just "database vacuum" or "vacuum of the entire > database" http://archives.postgresql.org/pgsql-committers/2008-12/msg00096.php It's "database-wide" now instead of "full-database". -- Greg Smith 2ndQuadrant US Baltimore, MD PostgreSQL Training, Services and Support greg@2ndQuadrant.com www.2ndQuadrant.us