Re: Unexpected chunk number

Chris Purcell <chris.purcell.39@gmail.com> writes:
> Would the best advice be to get a pg_dump, then drop the database
> entirely and rebuild it?
>>
>> Definitely.  It's entirely possible for pg_dump to dump successfully
>> from a database that still contains corruption.  An example:
>> broken indexes on user tables.  COPY just does a seqscan and never
>> looks
>> at the contents of indexes ...

> Just out of curiosity, why is it not possible to rebuild these
> indices entirely from scratch, dropping the defective file entirely,
> *without* reimporting into a fresh database?

See REINDEX.  But my point was that there may be undetected corruption.
If I were you I'd not rely on REINDEX to prevent all problems.

            regards, tom lane