Re: BUG #2685: Wrong charset of server messages on client

From: Sergiy Vyshnevetskiy <serg(at)vostok(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2685: Wrong charset of server messages on client
Date: 2006-10-10 20:00:38
Message-ID: Pine.LNX.4.64.0610102049080.24630@uanet.vostok.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, 10 Oct 2006, Sergiy Vyshnevetskiy wrote:

> On Tue, 10 Oct 2006, Tom Lane wrote:
>
>> Sergiy Vyshnevetskiy <serg(at)vostok(dot)net> writes:
>> > > It's not magic, it's from ICU patch. Want me to send you a copy? :)
>>
>> You're missing my point, which is that non-ICU locale support doesn't
>> necessarily recognize the same encoding names. We would have done this
>> years ago if we had a solution to that problem.
>
> We should use IANA-standard names. If it fails - it does nothing.
> Anybody porting PostgreSQL to new platform can go over the list and make a
> patch for their port.

Here is a new and improved patch, that closes security hole as well. To
prevent DOS attack we lock LC_MESSAGES as C for any database encoding that
we are unable to bind to our textdomain.

Attachment Content-Type Size
enc.diff text/plain 3.9 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2006-10-10 20:35:22 Re: BUG #2685: Wrong charset of server messages on client
Previous Message Sergiy Vyshnevetskiy 2006-10-10 17:01:58 Re: BUG #2685: Wrong charset of server messages on client