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 725ED3A2BE5 for ; Sun, 24 Oct 2004 22:59:29 +0100 (BST) 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 40073-02 for ; Sun, 24 Oct 2004 21:58:41 +0000 (GMT) Received: from mra04.ex.eclipse.net.uk (mra04.ex.eclipse.net.uk [212.104.129.139]) by svr1.postgresql.org (Postfix) with ESMTP id EC6E03A3FEB for ; Sun, 24 Oct 2004 22:59:07 +0100 (BST) Received: from localhost (localhost.localdomain [127.0.0.1]) by mra04.ex.eclipse.net.uk (Postfix) with ESMTP id BBB89133AFE for ; Sun, 24 Oct 2004 22:54:00 +0100 (BST) Received: from mra04.ex.eclipse.net.uk ([127.0.0.1]) by localhost (mra04.ex.eclipse.net.uk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 31190-01-33 for ; Sun, 24 Oct 2004 22:54:00 +0100 (BST) Received: from dev1 (unknown [82.152.145.238]) by mra04.ex.eclipse.net.uk (Postfix) with ESMTP id ED668133D1E for ; Sun, 24 Oct 2004 22:53:59 +0100 (BST) From: "Rod Dutton" To: Subject: Reindexdb and REINDEX Date: Sun, 24 Oct 2004 23:00:42 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0012_01C4BA1D.49978060" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcS6EpNUyDmOSHB3T9GPkaaJa1R8cQAAkrug X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Message-Id: <20041024215359.ED668133D1E@mra04.ex.eclipse.net.uk> X-Virus-Scanned: by Eclipse VIRUSshield at eclipse.net.uk X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.5 tagged_above=0.0 required=5.0 tests=HTML_40_50, HTML_MESSAGE X-Spam-Level: X-Archive-Number: 200410/402 X-Sequence-Number: 8878 This is a multi-part message in MIME format. ------=_NextPart_000_0012_01C4BA1D.49978060 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, I have had some performance problems recently on very large tables (10s of millions of rows). A vacuum full did make a large improvement and then dropping & re-creating the indexes also was very beneficial. My performance problem has now been solved. My question is: will using the contrib/reindexdb or REINDEX sql command do essentially the same job as dropping and re-creating the indexes. I.E. do you get a fully compacted and balanced index? If so then I could use contrib/reindexdb or REINDEX instead of drop/recreate. How is concurrency handled by contrib/reindexdb and REINDEX (I know you can create an index on the fly with no obvious lock outs)? Thanks, Rod ------=_NextPart_000_0012_01C4BA1D.49978060 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hi,
 
I have ha= d some=20 performance problems recently on very large tables (10s of millions of=20 rows).  A vacuum full did make a large improvement and then dropping &= amp;=20 re-creating the indexes also was very beneficial.  My performance prob= lem=20 has now been solved.
 
My questi= on is: will=20 using the contrib/reindexdb or REINDEX sql command do essentially the same = job=20 as dropping and re-creating the indexes.  I.E. do you get a fully comp= acted=20 and balanced index?  If so then I could use contrib/reindexdb or REIND= EX=20 instead of drop/recreate. 
 
How is co= ncurrency=20 handled by contrib/reindexdb and REINDEX (I know you can create an index on= the=20 fly with no obvious lock outs)?
 
Thanks,
 
Rod
 
------=_NextPart_000_0012_01C4BA1D.49978060--