X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 1C854D1C4C9; Tue, 29 Jul 2003 00:19:59 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 28848-06; Mon, 28 Jul 2003 21:19:04 -0300 (ADT) Received: from davinci.ethosmedia.com (209-128-84-228.bayarea.net [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id F0FBBD1C4B7; Mon, 28 Jul 2003 21:19:56 -0300 (ADT) Received: from [66.219.92.2] (HELO temoku) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 3355595; Mon, 28 Jul 2003 17:20:19 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Shankar K , pgsql-performance@postgresql.org Subject: Re: [PERFORM] Rebuild indexes Date: Mon, 28 Jul 2003 17:18:59 -0700 User-Agent: KMail/1.4.3 Cc: pgsql-admin@postgresql.org References: <20030728212905.79549.qmail@web21102.mail.yahoo.com> In-Reply-To: <20030728212905.79549.qmail@web21102.mail.yahoo.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200307281718.59127.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200307/367 X-Sequence-Number: 9707 Shankar, > Is there a better way to do this. comments are > appreciated. No. This is one of the major features in 7.4; FSM and VACUUM will manage= =20 indexes as well. Until then, we all suffer .... BTW, the REINDEX command is transaction-safe. So if your database has "lu= ll"=20 periods, you can run it without worrying that any updates will get turned= =20 back. --=20 -Josh Berkus Aglio Database Solutions San Francisco