Strange client encoding issue - Mailing list pgsql-admin

From Benjamin Krajmalnik
Subject Strange client encoding issue
Date
Msg-id F4E6A2751A2823418A21D4A160B689880E9243@fletch.stackdump.local
Whole thread Raw
Responses Re: Strange client encoding issue  (Ivo Rossacher <rossacher@bluewin.ch>)
List pgsql-admin
I am encountering a very strange client encoding issue.
From the logs on the server, I am getting the following:
 
canopy02# tail postgresql-2008-01-16_000000.log
2008-01-16 15:20:03 ESTERROR:  conversion between latin9 and LATIN1 is not supported
2008-01-16 15:20:03 ESTSTATEMENT:  set client_encoding to 'latin9'
2008-01-16 15:20:06 ESTLOG:  connection received: host=192.168.111.25 port=4236
2008-01-16 15:20:06 ESTLOG:  connection authorized: user=postgres database=ishield
2008-01-16 15:20:06 ESTERROR:  conversion between latin9 and LATIN1 is not supported
2008-01-16 15:20:06 ESTSTATEMENT:  set client_encoding to 'latin9'
2008-01-16 15:20:11 ESTLOG:  connection received: host=192.168.111.25 port=4253
2008-01-16 15:20:11 ESTLOG:  connection authorized: user=postgres database=ishield
2008-01-16 15:20:11 ESTERROR:  conversion between latin9 and LATIN1 is not supported
2008-01-16 15:20:11 ESTSTATEMENT:  set client_encoding to 'latin9'
The application logging data is using the PostgreSQL ANSI ODBC driver, version 08.01.02.00.
Database server is PostgreSQL 8.2.5 on i386-portbld-freebsd6.2, compiled by GCC cc (GCC) 3.4.6 [FreeBSD] 20060305
 
On page 2 of the datasources tab, in the Connect Settings tab, I have the following:
 
set client_encoding to 'latin1';
 
to force the encoding.
Any ideas on what may be creating this, and how to resolve it?
 
 
 

pgsql-admin by date:

Previous
From: Steve Holdoway
Date:
Subject: Re: Backup of live database
Next
From: Ivo Rossacher
Date:
Subject: Re: Strange client encoding issue