Skip site navigation (1) Skip section navigation (2)

Re: could not read block 77 of relation 1663/16385/388818775

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: Darren Reed <darrenr+postgres(at)fastmail(dot)net>
Cc: pgsql-bugs(at)postgresql(dot)org, an(at)clickware(dot)de, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, craig(at)postnewspapers(dot)com(dot)au
Subject: Re: could not read block 77 of relation 1663/16385/388818775
Date: 2009-02-22 14:41:36
Message-ID: 87mycev8in.fsf@oxford.xeocode.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Darren Reed <darrenr+postgres(at)fastmail(dot)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!

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2009-02-22 14:47:44
Subject: Re: BUG #4671: Cluster Initialisation Fails on FreeBSD
Previous:From: Darren ReedDate: 2009-02-22 11:29:54
Subject: Re: could not read block 77 of relation 1663/16385/388818775

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group