Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id 36B2A475C34 for ; Sun, 12 May 2002 11:22:41 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id DD1B9475B28 for ; Sun, 12 May 2002 11:22:39 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g4CFMSW29766; Sun, 12 May 2002 11:22:28 -0400 (EDT) To: Brian McCane Cc: pgsql-admin Subject: Re: VACUUM FULL In-reply-to: <20020511120040.X12454-100000@fw.mccons.net> References: <20020511120040.X12454-100000@fw.mccons.net> Comments: In-reply-to Brian McCane message dated "Sat, 11 May 2002 12:10:00 -0500" Date: Sun, 12 May 2002 11:22:28 -0400 Message-ID: <29763.1021216948@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200205/101 X-Sequence-Number: 4276 Brian McCane writes: > Would I possibly see another performance boost if I rebuilt the > indexes involved like I used to in 7.1.3? I still have the Perl script > sitting around here some place, but assumed from things said by you and > Bruce in the past few months about 7.2.x that it wouldn't be necessary > anymore. I guess I'll give it a try this weekend and see what happens. An occasional index rebuild (using either REINDEX or DROP/CREATE INDEX) is still worth doing for heavily updated tables, especially if the range of indexed values changes over time. That'll remain true until someone gets around to teaching btree indexes how to collapse out free space... regards, tom lane