| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | daniel(at)heroku(dot)com |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #7648: Momentary index corruption while in hot standby |
| Date: | 2012-11-09 23:35:58 |
| Message-ID: | 1352504158.26644.32.camel@sussancws0025 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, 2012-11-09 at 22:49 +0000, daniel(at)heroku(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Farina | 2012-11-09 23:57:06 | Re: BUG #7648: Momentary index corruption while in hot standby |
| Previous Message | daniel | 2012-11-09 22:49:33 | BUG #7648: Momentary index corruption while in hot standby |