From: Rod Dutton <rod@e-rm.co.uk>
To: pgsql-performance@postgresql.org
Subject: Reindexdb and REINDEX
Date: Sun, 24 Oct 2004 23:00:42 +0100
Message-ID: <20041024215359.ED668133D1E@mra04.ex.eclipse.net.uk> (raw)
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: rod@e-rm.co.uk
Subject: Re: Reindexdb and REINDEX
In-Reply-To: <20041024215359.ED668133D1E@mra04.ex.eclipse.net.uk>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox