Re: ERROR: conversion between UNICODE and LATIN1 - Mailing list pgadmin-hackers

From Andreas Pflug
Subject Re: ERROR: conversion between UNICODE and LATIN1
Date
Msg-id 416FB854.7090303@pse-consulting.de
Whole thread Raw
In response to Re: ERROR: conversion between UNICODE and LATIN1  (Troels Arvin <troels@arvin.dk>)
List pgadmin-hackers
Troels Arvin wrote:
> On Fri, 15 Oct 2004 09:46:04 +0000, Andreas Pflug wrote:
>
>
>>When does it fail? Enable sql logging for that.
>
>
> LOG:  connection received: host=127.0.0.1 port=36036
> LOG:  connection authorized: user=troels database=template1
> LOG:  statement: SELECT oid, pg_encoding_to_char(encoding) AS encoding, datlastsysoid
>           FROM pg_database WHERE datname='template1'
> LOG:  statement: set client_encoding to 'UNICODE'
> ERROR:  conversion between UNICODE and LATIN1 is not supported
>
> Output of "env | grep LANG":
> LANG=en_US.iso88591
>
> I have previously used pgadmin3 on this system with the same LANG setting
> without problems, but that was with PostgreSQL 7.4.

You're probably missing the appropriate conversions iso_8859_1_to_utf_8
and utf_8_to_iso_8859_1 (i.e. you probably dropped them). On a default
pgsql8, UNICODE<->LATIN1 is supported by default.

Regards,
Andreas

pgadmin-hackers by date:

Previous
From: Troels Arvin
Date:
Subject: Re: ERROR: conversion between UNICODE and LATIN1
Next
From: cvs@cvs.pgadmin.org
Date:
Subject: CVS Commit by andreas: change unsigned conversion for oids