From: Tom Lane <tgl@sss.pgh.pa.us>
To: John Lister <john.lister@kickstone.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: database corruption help
Date: Mon, 09 Feb 2009 14:34:04 -0500
Message-ID: <20151.1234208044@sss.pgh.pa.us> (raw)
In-Reply-To: <4990840C.4090900@kickstone.com>
References: <507152DDF8AB4DF093BD01A8BEC7C659@squarepi.com>
<17205.1234200693@sss.pgh.pa.us>
<AB15E89CD7FB4EBD9D76CC5F8D8B3D4E@squarepi.com>
<4990840C.4090900@kickstone.com>
John Lister <john.lister@kickstone.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, john.lister@kickstone.com
Subject: Re: database corruption help
In-Reply-To: <20151.1234208044@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox