John R Pierce wrote:
> It appears you have at least one corrupt block. Where there's one,
> there's often more.
>
> I think i'd do a reindex all. and Imight even do a pg_dumpall,
> re-initdb, and restore said dumpall to be safeest. to be really
> safe, stop pg, and take a file system backup first, incase more
> serious problems show up during the reindex or dump process
I would add a basic check of the system hardware to that list. In
particular, I'm always suspicious of memory errors when seeing strange
PANIC messages. A quick check for SMART errors on the hard drives would
be in order too.
--
Greg Smith 2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
greg@2ndQuadrant.com www.2ndQuadrant.com
