The following bug has been logged online:

Bug reference: 1484
Logged by: Johann Gregorich
Email address: johann.gregorich (AT) itgconsulting (DOT) at
PostgreSQL version: 8.0.0
Operating system: Linux and Windows XP
Description: client gets the wrong character set
Details:

Hi,

when connecting from Win XP (german) to pg 8.0.0 (unicode database on suse
linux 9.2) via ODBC we do not get as expected Latin9 charcter set from the
backend, but UTF8.

This results in a odbc message '....wrong unicode character...'

We tried a workaround to set the client character set after every cursor
connect (before executing the statement), but no chance.

Has somebody an idea how to overcome this mess?

Regards
Hans

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match