From: | Alfred Perlstein <bright(at)wintelcom(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | will trillich <will(at)serensoft(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: unbalanced indexes -> fixed via dump/restore? |
Date: | 2001-03-08 07:43:55 |
Message-ID: | 20010307234355.C18351@fw.wintelcom.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
* Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> [010307 14:30] wrote:
> will trillich <will(at)serensoft(dot)com> writes:
> > A)
> > pg_dump -c mydb > db.out.sql
> > and then
> > psql mydb < db.out.sql
> > periodically?
>
> > or is it better to
>
> > B) merely 'reindex' on occasion?
>
> Plain old DROP INDEX / CREATE INDEX is probably the best-trodden path.
> Your (A) seems like vastly more work than is needed. (B) might be
> marginally easier than DROP/CREATE, but I'm not sure how much I trust
> REINDEX; it's not been around all that long.
Is there a way to do this atomically, meaning so that no one can
get at the table after dropping, but before recreating the index?
lock the table during?
--
-Alfred Perlstein - [bright(at)wintelcom(dot)net|alfred(at)freebsd(dot)org]
From | Date | Subject | |
---|---|---|---|
Next Message | dev | 2001-03-08 09:17:33 | CONTRIB: int8 sequence simulator |
Previous Message | Stefan Waidele jun. | 2001-03-08 07:19:55 | Re: Paradox, dbf and PostgreSQL ? |