Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 72A799FB55A for ; Tue, 19 Jun 2007 14:43:22 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 45401-08 for ; Tue, 19 Jun 2007 14:43:17 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from fed1rmmtao103.cox.net (fed1rmmtao103.cox.net [68.230.241.43]) by postgresql.org (Postfix) with ESMTP id 7F1C89FB526 for ; Tue, 19 Jun 2007 14:43:18 -0300 (ADT) Received: from fed1rmimpo01.cox.net ([70.169.32.71]) by fed1rmmtao103.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20070619174316.ERWL1594.fed1rmmtao103.cox.net@fed1rmimpo01.cox.net> for ; Tue, 19 Jun 2007 13:43:16 -0400 Received: from bwlaptop ([68.101.98.29]) by fed1rmimpo01.cox.net with bizsmtp id DVjD1X0030e2M1w0000000; Tue, 19 Jun 2007 13:43:17 -0400 Message-ID: <004201c7b299$4ceb7bf0$b601a8c0@bwlaptop> From: "Bill Willits" To: Subject: reindex in v8.2 Date: Tue, 19 Jun 2007 10:43:07 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_003F_01C7B25E.9F9BDB50" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.339 tagged_above=0 required=5 tests=AWL=0.203, BAYES_50=0.001, HTML_50_60=0.134, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200706/185 X-Sequence-Number: 25853 This is a multi-part message in MIME format. ------=_NextPart_000_003F_01C7B25E.9F9BDB50 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello: We are in the process of upgrading posgres from v7.3.9 to v8.2.4 In our = current environment (v7.3), we run a reindex operation on all tables to = recover space and improve performance (we have several tables with high = insert/update load - no deletes). Is it likely that the reindex will = still be beneficial after the upgrade? Or has the pg code changed such = that this operation is obsolete? Thanks in advance. Bill Willits ------=_NextPart_000_003F_01C7B25E.9F9BDB50 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello:
 
We are in the process of upgrading = posgres from=20 v7.3.9 to v8.2.4  In our current environment (v7.3), we run a = reindex=20 operation on all tables to recover space and improve performance (we = have=20 several tables with high insert/update load - no deletes).  Is it = likely=20 that the reindex will still be beneficial after the = upgrade?  Or=20 has the pg code changed such that this operation is = obsolete?
 
Thanks in advance.
Bill Willits
------=_NextPart_000_003F_01C7B25E.9F9BDB50--