Re: Unexpected chunk number - Mailing list pgsql-bugs

From Chris Purcell
Subject Re: Unexpected chunk number
Date
Msg-id AA613804-69E9-4C3D-A880-A274A2940407@gmail.com
Whole thread Raw
In response to Re: Unexpected chunk number  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Unexpected chunk number
List pgsql-bugs
>> 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?

Cheers,
Chris

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Unexpected chunk number
Next
From: Tom Lane
Date:
Subject: Re: Unexpected chunk number