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

Andres Freund <andres@2ndquadrant.com> writes:
> On Thursday, September 20, 2012 11:38:52 PM Tom Lane wrote:
>> Sure, but what about the heap?  The case I was speculating about was
>> that the heap had been truncated, but because of the corruption problem,
>> the index still had heap pointers in it.  We don't know what file 16585
>> is supposed to be.

> Wouldn't the truncation have created a completely new index relation?

If it were an actual TRUNCATE, yeah.  But it could be a case of VACUUM
truncating a now-empty table to zero blocks.

But nothing like this would explain the OP's report that corruption is
completely reproducible for him.  So I like your theory about hash index
use better.  We really oughta get some WAL support in there.

            regards, tom lane