Re: BUG #7648: Momentary index corruption while in hot standby

On Fri, 2012-11-09 at 22:49 +0000, daniel@heroku.com wrote:
> PGError: ERROR: could not read block 556642 in file "base/16385/2904143.4":
> read only 0 of 8192

Does that seem wildly off to you, or a little off? Do you think that
block may have existed in the past, but was truncated by a VACUUM or
something?

Just to clarify, that file belongs to the index in question, right? It's
not the heap pointed to by the index?

> Immediately thereafter, no occurrences of the error resurfaced and any
> attempts to reproduce the issue with an identical query were met with
> failure.

Or a lack of failure, I presume.

> This is reading from a 9.0.8 Postgres.

Any indication whether it's present on other versions or does it appear
to be isolated to 9.0.X?

Regards,
    Jeff Davis