| From: | daniel(at)heroku(dot)com |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #7648: Momentary index corruption while in hot standby |
| Date: | 2012-11-09 22:49:33 |
| Message-ID: | E1TWxOH-0002Lx-QA@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 7648
Logged by: Daniel Farina
Email address: daniel(at)heroku(dot)com
PostgreSQL version: 9.0.9
Operating system: Ubuntu 10.04
Description:
At more or less one point in time exactly (the same second, at minimum), a
couple of errors were raised on a hot standby while performing query access
that would nominally suggest corruption were raised:
PGError: ERROR: could not read block 556642 in file "base/16385/2904143.4":
read only 0 of 8192
Immediately thereafter, no occurrences of the error resurfaced and any
attempts to reproduce the issue with an identical query were met with
failure.
On investigation, this relfile is a fairly common beast: an integer btree
index being used for row identification (e.g. serial).
This is reading from a 9.0.8 Postgres.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2012-11-09 23:35:58 | Re: BUG #7648: Momentary index corruption while in hot standby |
| Previous Message | rep.dot.nop | 2012-11-09 09:57:45 | BUG #7644: Missing implicit types of Result and failing type-conversion |