Ran with this change. Didn't take long to hit it.
Let me know if there's anything else I can do.
[2005-11-16 11:59:29.015 ] 4904 <dtr dtr 165.219.88.22(60649)> LOG:
read failed on relation 1663/16385/1494810: -1 bytes, 1450
[2005-11-16 11:59:29.015 ] 4904 <dtr dtr 165.219.88.22(60649)> ERROR:
could not read block 25447 of relation 1663/16385/1494810: Invalid
argument
>>> Tom Lane <tgl@xxxxxxxxxxxxx> >>>
I think this is just cosmetic, but try %ld instead of %d in the elog
format strings.
---------------------------(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
