Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 11CCF1337BEA for ; Wed, 6 Oct 2010 01:42:03 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 95341-03 for ; Wed, 6 Oct 2010 04:41:54 +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 7ABFE1337BE5 for ; Wed, 6 Oct 2010 01:41:53 -0300 (ADT) Received: from [192.168.1.6] (static-71-179-240-8.bltmmd.fios.verizon.net [71.179.240.8]) by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis) id 0MPKwG-1P7jXM2w0u-0050j4; Wed, 06 Oct 2010 06:41:53 +0200 Message-ID: <4CABFE0F.5040500@2ndquadrant.com> Date: Wed, 06 Oct 2010 00:41:51 -0400 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Kieren Scott CC: pgsql-admin@postgresql.org Subject: Re: vacuum full table - internals in 8.3 References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------070502050908000807000101" X-Provags-ID: V02:K0:ijwJlCkpnNFrJKjV5mc75OtrqKt9/zt0akk123QzWoS AqMOUwY2swtWVrF2pp6PdjRj+wvwK6STxDNoQXI/lLmtaPsF3d dUJ621dWdlrp7Aha4uv6+4OET6fUlZ0PAOHtNcTkGPHOCdg98V l1oj926VJ6+s8427J1+6mjSpdaYH6FJUMsJdrHpGnzEQ3MHfJH luaTnJV8gsGjDAnpzwfnAAHa/VgQcUB4SvvVDWqpuc= 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201010/52 X-Sequence-Number: 35793 This is a multi-part message in MIME format. --------------070502050908000807000101 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Kieren Scott wrote: > I'm trying to understand what is going on internally when doing a > VACUUM FULL on a table in 8.3. The info you've gotten from Kevin is all correct, but you may find some of the additional trivia in this area collected at http://wiki.postgresql.org/wiki/VACUUM_FULL interesting as well. -- Greg Smith, 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services and Support www.2ndQuadrant.us Author, "PostgreSQL 9.0 High Performance" Pre-ordering at: https://www.packtpub.com/postgresql-9-0-high-performance/book --------------070502050908000807000101 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Kieren Scott wrote:
I'm trying to understand what is going on internally when doing a VACUUM FULL on a table in 8.3.

The info you've gotten from Kevin is all correct, but you may find some of the additional trivia in this area collected at http://wiki.postgresql.org/wiki/VACUUM_FULL interesting as well.

-- 
Greg Smith, 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD
PostgreSQL Training, Services and Support  www.2ndQuadrant.us
Author, "PostgreSQL 9.0 High Performance"    Pre-ordering at:
https://www.packtpub.com/postgresql-9-0-high-performance/book
--------------070502050908000807000101--