Re: could not read block 77 of relation 1663/16385/388818775 - Mailing list pgsql-bugs

From Gregory Stark
Subject Re: could not read block 77 of relation 1663/16385/388818775
Date
Msg-id 87mycev8in.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: could not read block 77 of relation 1663/16385/388818775  (Darren Reed <darrenr+postgres@fastmail.net>)
Responses Re: could not read block 77 of relation 1663/16385/388818775  (Darren Reed <darrenr+postgres@fastmail.net>)
List pgsql-bugs
Darren Reed <darrenr+postgres@fastmail.net> writes:

> ERROR:  could not read block 1 of relation 1664/0/1233: read only 0 of
> 8192 bytes

FWIW this is pg_shdepend_reference_index which is actually a bit special. It's
a "shared" relation which means it spans all your databases. Your reindex
didn't rebuild to. To reindex it you would have to shut down postgres and run
REINDEX in postgres in "standalone" mode.

> I suppose the logical thing for me to do is go back to 8.2.6.

I think it would be more interesting to know how you got into this situation.
When you ran initdb did anything unusual happen? Is it possible anything later
truncated these files?

There's no reason I can imagine 8.3 would be any more susceptible to this than
8.2. And certainly no reason you would want to use a year-old release of 8.2
missing a year's worth of bug fixes and security fixes. The current release of
8.2 is 8.2.12.

--
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com
  Ask me about EnterpriseDB's 24x7 Postgres support!

pgsql-bugs by date:

Previous
From: Darren Reed
Date:
Subject: Re: could not read block 77 of relation 1663/16385/388818775
Next
From: Tom Lane
Date:
Subject: Re: BUG #4671: Cluster Initialisation Fails on FreeBSD