| From: | Neil Conway <nconway(at)klamath(dot)dyndns(dot)org> |
|---|---|
| To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | sthomas(at)townnews(dot)com, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Contrib reindex script: |
| Date: | 2002-06-13 18:37:07 |
| Message-ID: | 20020613143707.7faf4e84.nconway@klamath.dyndns.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 13 Jun 2002 13:13:29 -0400 (EDT)
"Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> wrote:
> First, I think we need a section in the admin/maintenance manual talking
> about reindex. (We already have vacuum there, and I think reindex is
> something that periodically also should be done.)
One simple improvement would be to change the documentation's view of
REINDEX -- at the moment, it says that it's only useful for rebuilding
"corrupted indexes". If it's a legitimate maintainence activity for
certain query loads, it should get a more positive spin.
Also, could we enhance REINDEX to not require an exclusive table lock?
Without looking at the code, I would think that we could at least allow
for SELECTs (using seqscans or other indexes) while a REINDEX is running.
Cheers,
Neil
--
Neil Conway <neilconway(at)rogers(dot)com>
PGP Key ID: DB3C29FC
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Seidman | 2002-06-13 18:46:45 | odd date behavior |
| Previous Message | Marc G. Fournier | 2002-06-13 18:13:46 | Re: Once again, nntp://news.postgresql.org is down |