Re: BUG #4180: PANIC while PQExec on Client with differen locale from database

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "bishop(dot)gis" <bishop(dot)gis(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgreSQL(dot)org
Subject: Re: BUG #4180: PANIC while PQExec on Client with differen locale from database
Date: 2008-05-19 03:02:16
Message-ID: 11013.1211166136@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

[ please keep the mailing list cc'd on discussions ]

"bishop.gis" <bishop(dot)gis(at)gmail(dot)com> writes:
> This is result executing the same command with client_encoding = UTF8.
> ERROR: =CE=C5=D7=C5=D2=CE=C1=D1 =
> =D0=CF=D3=CC=C5=C4=CF=D7=C1=D4=C5=CC=D8=CE=CF=D3=D4=D8 =C2=C1=CA=D4 =
> =C9=CD=D1 =CB=CF=C4=C9=D2=CF=D7=CB=C9 "UTF8": 0xcdee (on
> English -- invalid UTF-8 byte sequence detected near byte 0xcdee)
> =F0=EF=E4=F3=EB=E1=FA=EB=E1: This error can also happen if the byte =
> sequence does not match
> the encoding expected by the server, which is controlled by
> "client_encoding".

Hmm ... I don't read Russian, but I'm quite certain that what you sent
isn't in UTF8. Perhaps it is in KOI8-R?

This lends some weight to the theory I suggested that gettext() is
failing to return UTF8 on Windows. That could be a red herring, since
it's possible the encoding got changed when you copied the text into
your mail message, but the theory seems to explain the observed facts
so far.

What locale settings are you using --- particularly lc_ctype and
lc_messages?

regards, tom lane

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Eugen.Konkov 2008-05-19 17:18:59 Win32: Postgre 8.3.1 does not work with Active perl 5.10
Previous Message Tom Lane 2008-05-18 21:01:42 Re: BUG #4182: Enum in Foreign Key broken