From: Ivo Rossacher <rossacher@bluewin.ch>
To: pgsql-admin@postgresql.org
Subject: Re: Strange client encoding issue
Date: Wed, 16 Jan 2008 23:32:17 +0100
Message-ID: <200801162332.17449.rossacher@bluewin.ch> (raw)
In-Reply-To: <F4E6A2751A2823418A21D4A160B689880E9243@fletch.stackdump.local>
References: <F4E6A2751A2823418A21D4A160B689880E9243@fletch.stackdump.local>
The encoding of the client can not be convertet to the encoding of the server.
In the manual in chapter 21.2 you can find the list of supported encodings and
possible conversions between them.
The conversion between latin1 and latin9 is not supported.
For a latin9 database you can use the client encoding latin9 or utf8 but not
latin1.
Best regards
Ivo
Am Mittwoch, 16. Januar 2008 21.30:42 schrieb Benjamin Krajmalnik:
> 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?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: rossacher@bluewin.ch
Subject: Re: Strange client encoding issue
In-Reply-To: <200801162332.17449.rossacher@bluewin.ch>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox