| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: REINDEX slow? |
| Date: | 2004-04-13 03:00:49 |
| Message-ID: | 87ekqseg4e.fsf@stark.xeocode.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Edmund Dengler <edmundd(at)eSentire(dot)com> writes:
> Alternatively, if I created a second index, and then dropped the first,
> would this be faster (though I would suppose that an ANALYZE would need to
> be done to recognize the utility of the new index, thereby negating any
> speed improvements)?
Currently analyze doesn't check what indexes exist, it analyzes all the
columns of the table anyways. However I think this won't be true in 7.5 when
there are expression indexes, and there has been talk of changing this in
future to take into account indexes and foreign keys.
I don't think it would be any faster but it might avoid downtime. Reindex
seems to block any use of the index until the reindex completes, while doing
this two-step would avoid blocking queries. I haven't tried it myself though
so I'm not sure what gotchas might arise.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dennis Gearon | 2004-04-13 04:34:35 | specifics about BIT(n) types |
| Previous Message | Christopher Browne | 2004-04-13 01:33:08 | Re: Data Encryption in PostgreSQL, and a Tutorial. |