From: | Alvaro Herrera <alvherre(at)atentus(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Doug McNaught <doug(at)wireboard(dot)com>, carex <bk226157(at)skynet(dot)be>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: index files still growing |
Date: | 2001-10-24 14:31:04 |
Message-ID: | Pine.LNX.4.33L2.0110241125140.25995-100000@aguila.protecne.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 24 Oct 2001, Tom Lane wrote:
> Doug McNaught <doug(at)wireboard(dot)com> writes:
> >> My solution is to DROP & CREATE my indexes files once
> >> a week.
>
> > Your solution is currently the only one available. Not pretty, but it
> > works.
>
> REINDEX is a marginally prettier answer; at least you don't have to
> remember the index parameters. Shrinking indexes on-the-fly is still
> on the TODO list.
But at least in 7.1 REINDEX has to be run under stand-alone Postgres, or
so say the docs:
REINDEX is used to recover corrupted system indexes. In order to run
REINDEX command, postmaster must be shut down and stand-alone Postgres
should be started instead with options -O and -P (an option to ignore
system indexes).
Whereas the DROP INDEX/CREATE INDEX method works on-the-fly. You may end
up running a seqscan somewhere, but that's not so big a problem, IMHO.
--
Alvaro Herrera (<alvherre[(at)]atentus(dot)com>)
The eagle never lost so much time as
when he submitted to learn from the crow. (Nobody)
From | Date | Subject | |
---|---|---|---|
Next Message | John Fabiani | 2001-10-24 14:57:48 | Re: Installation problems |
Previous Message | qk22 | 2001-10-24 14:23:59 | Re: Can not input large text data |