Chris Purcell <chris(dot)purcell(dot)39(at)gmail(dot)com> writes:
>> That will get you past the reported problem, but I wonder what other
>> corruption is lurking ... once you've managed to pg_dump you'd better
>> inspect the data very carefully.
> 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 ...
regards, tom lane
In response to
pgsql-bugs by date
|Next:||From: Chris Purcell||Date: 2006-09-12 21:15:03|
|Subject: Re: Unexpected chunk number |
|Previous:||From: vodhner||Date: 2006-09-12 18:23:03|
|Subject: pgsql on Solaris 10|