Re: MULE_INTERNAL translation to win1250

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: NTPT <ntpt(at)centrum(dot)cz>, pgsql-general(at)postgresql(dot)org
Subject: Re: MULE_INTERNAL translation to win1250
Date: 2007-01-29 05:15:04
Message-ID: 20070129051504.GA85598@winnie.fuhr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sun, Jan 28, 2007 at 07:27:12PM -0700, Michael Fuhr wrote:
> I wonder if the OP is doing something like this:
[...]
> test=> INSERT INTO test VALUES (E'\202\232'); -- \202=0x82, \232=0x9a

Another possibility, perhaps more likely, is that some connection
didn't set client_encoding to win1250 before it inserted win1250-encoded
data; in that case the data was probably treated as LATIN2 and
stored without conversion. When a connection with client_encoding
set to win1250 tries to fetch the data, conversion is attempted and
fails because some LATIN2 values don't have win1250 mappings.

--
Michael Fuhr

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Pierre Thibaudeau 2007-01-29 06:47:15 convert(USING utf8_to_iso_8859_15) on Windows
Previous Message Joshua D. Drake 2007-01-29 03:41:28 Re: Load balancing across disks