Strange client encoding issue
am 16.01.2008 21:30:42 von Benjamin KrajmalnikThis is a multi-part message in MIME format.
------_=_NextPart_001_01C8587E.AA4FED97
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
I am encountering a very strange client encoding issue.
From the logs on the server, I am getting the following:
=20
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=3D192.168.111.25
port=3D4236
2008-01-16 15:20:06 ESTLOG: connection authorized: user=3Dpostgres
database=3Dishield
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=3D192.168.111.25
port=3D4253
2008-01-16 15:20:11 ESTLOG: connection authorized: user=3Dpostgres
database=3Dishield
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
=20
On page 2 of the datasources tab, in the Connect Settings tab, I have
the following:
=20
set client_encoding to 'latin1';
=20
to force the encoding.
Any ideas on what may be creating this, and how to resolve it?
=20
=20
=20
------_=_NextPart_001_01C8587E.AA4FED97
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
charset=3Dus-ascii">
encountering a=20
very strange client encoding issue.
the logs on the=20
server, I am getting the following:
postgresql-2008-01-16_000000.log
2008-01-16 15:20:03 ESTERROR: =20
conversion between latin9 and LATIN1 is not supported
2008-01-16 =
15:20:03=20
ESTSTATEMENT: set client_encoding to 'latin9'
2008-01-16 =
15:20:06=20
ESTLOG: connection received: host=3D192.168.111.25 =
port=3D4236
2008-01-16=20
15:20:06 ESTLOG: connection authorized: user=3Dpostgres=20
database=3Dishield
2008-01-16 15:20:06 ESTERROR: conversion =
between=20
latin9 and LATIN1 is not supported
2008-01-16 15:20:06 =
ESTSTATEMENT: =20
set client_encoding to 'latin9'
2008-01-16 15:20:11 ESTLOG: =
connection=20
received: host=3D192.168.111.25 port=3D4253
2008-01-16 15:20:11 =
ESTLOG: =20
connection authorized: user=3Dpostgres database=3Dishield
2008-01-16 =
15:20:11=20
ESTERROR: conversion between latin9 and LATIN1 is not=20
supported
2008-01-16 15:20:11 ESTSTATEMENT: set client_encoding =
to=20
'latin9'
application=20
logging data is using the PostgreSQL ANSI ODBC driver, version=20
08.01.02.00.
is PostgreSQL 8.2.5 on i386-portbld-freebsd6.2, compiled by GCC cc =
(GCC)=20
3.4.6 [FreeBSD] 20060305
page 2 of the=20
datasources tab, in the Connect Settings tab, I have the=20
following:
client_encoding=20
to 'latin1';
force the=20
encoding.
ideas on what=20
may be creating this, and how to resolve it?
------_=_NextPart_001_01C8587E.AA4FED97--