| From: | Edmund Dengler <edmundd(at)eSentire(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | REINDEX slow? |
| Date: | 2004-04-12 02:05:58 |
| Message-ID: | Pine.BSO.4.58.0404112159120.28505@cyclops4.esentire.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Howdy all!
Quick question regarding REINDEX. I have a large table with 1077455 rows.
I have an index on the table with a WHERE clause that limits the rows to
around 10-50. When I REINDEX this index, it takes on the order of a minute
to do the reindex. Question: Does a REINDEX use the old version to build
the new version, or is it the semantic equivalent to "drop index; build
new index". If the first, any thoughts on why it is taking so long to
reindex? If the second, any particular reason not to use the current
(though possibly bloated) index to reduce work (essentially, all we are
doing is recompacting the same info as the original index with a
rebalance)?
Regards!
Ed
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-04-12 02:23:32 | Re: ERROR: REINDEX DATABASE: Can be executed only on the currently open database. |
| Previous Message | Clodoaldo Pinto Neto | 2004-04-11 23:01:33 | ERROR: REINDEX DATABASE: Can be executed only on the currently open database. |