From: Tom Lane <tgl@sss.pgh.pa.us>
To: Diego Fernández Slezak <dfslezak@gmail.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: ERROR: could not read block
Date: Sat, 21 May 2011 11:16:09 -0400
Message-ID: <1278.1305990969@sss.pgh.pa.us> (raw)
In-Reply-To: <BANLkTinMSGGm+6+tgKVZMHXJbO3ZoE_9LQ@mail.gmail.com>
References: <BANLkTinK8-Gz01ARiAryB0Hx+oJac=D=HA@mail.gmail.com>
<BANLkTinMSGGm+6+tgKVZMHXJbO3ZoE_9LQ@mail.gmail.com>
=?ISO-8859-1?Q?Diego_Fern=E1ndez_Slezak?= <dfslezak@gmail.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, dfslezak@gmail.com
Subject: Re: ERROR: could not read block
In-Reply-To: <1278.1305990969@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox