Re: Unexpected chunk number

From: Chris Purcell <chris(dot)purcell(dot)39(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org, Sunir Shah <sunir(at)sunir(dot)org>
Subject: Re: Unexpected chunk number
Date: 2006-09-12 21:15:03
Message-ID: AA613804-69E9-4C3D-A880-A274A2940407@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2006-09-12 21:39:42 Re: Unexpected chunk number
Previous Message Tom Lane 2006-09-12 20:44:16 Re: Unexpected chunk number