alex <[EMAIL PROTECTED]> writes:
> Summary
> ==========
> Various errors like:
> "invalid page header in block 8658 of relation",
> "could not open segment 2 of relation 1663/77142409/266753945 (target
> block 809775152)",
> "ERROR: could not access status of transaction 2134240 DETAIL: could
> not open file "pg_clog/0002": File not found",
> "CEST PANIC: right sibling's left-link doesn't match"
Ick. For any one of those errors, I would've thought it was Postgres'
fault, but when you have several it's not so clear. Kernel or hardware
flakiness have to be considered as alternative explanations.
> on the following system:
> Postgres 8.1.8
> SUsE Linux Kernel 2.6.13-15.8-smp
2.6.13 is not the latest, nor even close --- can you update the kernel
and see if things get better?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
