| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | John Lister <john(dot)lister(at)kickstone(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: database corruption help |
| Date: | 2009-02-09 19:34:04 |
| Message-ID: | 20151.1234208044@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
John Lister <john(dot)lister(at)kickstone(dot)com> writes:
> Although saying that..
> reindex now works, but doing a vacuum verbose complains that the index
> is out of step with the table and i should reindex..
> would i be better shutting the db down, restarting in standalone mode
> (and also using the -P option) before reindexing?
Yeah, if you have reason not to trust the system indexes then -P is
a good idea until they are fixed. Standalone mode per se isn't that
important --- you could do this from a regular session with -P specified
via PGOPTIONS.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Lister | 2009-02-09 20:09:22 | Re: database corruption help |
| Previous Message | John Lister | 2009-02-09 19:20:40 | Re: database corruption help |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-02-09 19:54:05 | Re: [PATCHES] GIN improvements |
| Previous Message | John Lister | 2009-02-09 19:20:40 | Re: database corruption help |