X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 39F588BA29D for ; Tue, 15 Feb 2005 05:32:30 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 58969-03 for ; Tue, 15 Feb 2005 05:32:24 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id A278D8BA287 for ; Tue, 15 Feb 2005 05:32:22 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j1F5UULR008500; Tue, 15 Feb 2005 00:30:31 -0500 (EST) To: "Iain" Cc: "Michael Ryan S. Puncia" , pgsql-performance@postgresql.org Subject: Re: VACCUM FULL ANALYZE PROBLEM In-reply-to: <009201c51306$6e9ece80$7201a8c0@mst1x5r347kymb> References: <200502150202.j1F22flW029903@mail.census.gov.ph> <009201c51306$6e9ece80$7201a8c0@mst1x5r347kymb> Comments: In-reply-to "Iain" message dated "Tue, 15 Feb 2005 11:31:14 +0900" Date: Tue, 15 Feb 2005 00:30:30 -0500 Message-ID: <8499.1108445430@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.007 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200502/228 X-Sequence-Number: 10557 "Iain" writes: >> another way to speed up full vacuum? > Hmmm... a full vacuum may help to re-organize the structure of modified > tables, but whether this is significant or not is another matter. Actually, VACUUM FULL is designed to work nicely for the situation where a table has say 10% wasted space and you want the wasted space all compressed out. When there is a lot of wasted space, so that nearly all the rows have to be moved to complete the compaction operation, VACUUM FULL is not a very good choice. And it simply moves rows around, it doesn't modify the rows internally; so it does nothing at all to reclaim space that would have been freed up by DROP COLUMN operations. CLUSTER is actually a better bet if you want to repack a table that's suffered a lot of updates or deletions. In PG 8.0 you might also consider one of the rewriting variants of ALTER TABLE. regards, tom lane