All
I have a recurrent error in my postgres 8.0.4 on redhat 9 (yes, I know
its old - first things first...) server. It only occurs from the
MSAccess/Windows clients I have, not from Java/JDBC or
pgAdminIII/Windows clients; hence the question here.

The log shows (anonymised) up to 6 times a second while a user is
active:

Feb 8 16:03:28 (server) postgres[8625]: [7-1] 2006-02-08
16:03:28 GMT (user)(database) ERROR: conversion between latin9 and
LATIN1 is not supported.


Now, I have added statement debugging to the log together with a "set
client_encoding to 'latin1'" in the ODBC driver, and got this:

Feb 8 15:48:18 (server) postgres[8277]: [6-1] 2006-02-08
15:48:18 GMT (user) (database) LOG: statement: select version()
Feb 8 15:48:18 (server) postgres[8277]: [7-1] 2006-02-08
15:48:18 GMT (user) (database) LOG: statement: set DateStyle to 'ISO'
Feb 8 15:48:18 (server) postgres[8277]: [8-1] 2006-02-08
15:48:18 GMT (user) (database) LOG: statement: set geqo to 'OFF'
Feb 8 15:48:18 (server) postgres[8277]: [9-1] 2006-02-08
15:48:18 GMT (user) (database) LOG: statement: set extra_float_digits
to 2
Feb 8 15:48:18 (server) postgres[8277]: [10-1] 2006-02-08
15:48:18 GMT (user) (database) LOG: statement: set client_encoding to
'latin1'
Feb 8 15:48:18 (server) postgres[8277]: [11-1] 2006-02-08
15:48:18 GMT (user) (database) LOG: statement: select oid from pg_type
where typname='lo'
Feb 8 15:48:18 (server) postgres[8277]: [12-1] 2006-02-08
15:48:18 GMT (user) (database) LOG: statement: select
pg_client_encoding()
Feb 8 15:48:18 (server) postgres[8277]: [13-1] 2006-02-08
15:48:18 GMT (user) (database) LOG: statement: set client_encoding to
'latin9'
Feb 8 15:48:18 (server) postgres[8277]: [14-1] 2006-02-08
15:48:18 GMT (user) (database) ERROR: conversion between latin9 and
LATIN1 is not supported

You can clearly see my latin1 request followed shortly by the latin9. I
have examined the ODBC code and it looks like the culprit is a code page
of 1252.

Am I tracing this right? What do I do about? Suggestions, please!

Tim Clarke

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Hello,

I'm not much experienced in encoding.

> You can clearly see my latin1 request followed shortly by the latin9. I
> have examined the ODBC code and it looks like the culprit is a code page
> of 1252.

It could be interesting to see mylog output from Windows.
I don't understand well why it choose latin1 and then latin9.
Don't you specify 'set client_encoding to latin1' in DataSource
settings?
I'm new developer since 08.01 version so please be patient with me.

> Am I tracing this right? What do I do about? Suggestions, please!

You could use way of unicode driver. It use UTF-8 so no error occurs
with latin 1 x latin 9.
It means you may use "PostgreSQL Unicode" driver instead of
"PostgreSQL ANSI"

To other developers:
Another one user points to problems with win1252 -> Latin 9 mapping.
It seems to me that Latin 9 isn't right default choise for win1252.
What do you mean?

Regards,

Luf

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend