Re: ERROR: could not read block

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Diego Fernández Slezak <dfslezak(at)gmail(dot)com>
Cc: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: ERROR: could not read block
Date: 2011-05-21 15:16:09
Message-ID: 1278.1305990969@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

=?ISO-8859-1?Q?Diego_Fern=E1ndez_Slezak?= <dfslezak(at)gmail(dot)com> writes:
> Hello everybody,
> I had a hard drive failure last week. After lots of effort I've been able to
> backup a 700GB database, with only one file with corruption.

> When I do some big queries, it throws me errors on this faulty file:
> could not read block 390041 of relation 1663/350994/351212: read only 0 of
> 8192 bytes

I'm guessing this is the result of an index entry pointing to a block
that's not there --- either the index is corrupted, or you lost some
data. In any case, reindexing the table ought to get rid of this error.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Guillaume Lelarge 2011-05-21 23:10:55 Re: Reg:import issue in PostgresSQL server
Previous Message Tom Lane 2011-05-21 15:11:12 Re: Who is causing all this i/o?