"Peter Darley" <[EMAIL PROTECTED]> writes:
> So, long and short, I think that everything should be SQL_ASCII, but
> even
> when it is, I get the error.
There is no way you're going to get that error if the encoding setting
is SQL_ASCII, so better look again. "SHOW server_encoding" and "SHOW
client_encoding" might be revealing.
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
