Re: BUG #7562: could not read block 0 in file "base/16385/16585": read only 0 of 8192 bytes

From: Bernd Helmle <mailings(at)oopsware(dot)de>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org, mayank(dot)mittal(dot)1982(at)hotmail(dot)com
Subject: Re: BUG #7562: could not read block 0 in file "base/16385/16585": read only 0 of 8192 bytes
Date: 2012-09-21 09:34:49
Message-ID: 873D76786B6DA97F0EBD16ED@apophis.credativ.lan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

--On 21. September 2012 10:25:50 +0200 Andres Freund
<andres(at)2ndquadrant(dot)com> wrote:

>> We had a similar issue at a customer site. The server was shut down for
>> updating it from 9.1.4 to 9.1.5, after starting it again the log was
>> immediately cluttered with
> How was it shutdown? -m fast or -m immediate?
>

-m fast

>> ERROR: could not read block 251 in file "base/6447890/7843708": read
>> only 0 of 8192 bytes
> So, not block 0. How many blocks does the new index contain?

255 blocks according to its current size.

--
Thanks

Bernd

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Amit kapila 2012-09-21 11:18:01 Re: [BUGS] BUG #7534: walreceiver takes long time to detect n/w breakdown
Previous Message Mayank Mittal 2012-09-21 08:42:44 Re: BUG #7562: could not read block 0 in file "base/16385/16585": read only 0 of 8192 bytes