From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: More message encoding woes |
Date: | 2009-03-30 17:47:58 |
Message-ID: | 49D105CE.5010705@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
>> Tom Lane wrote:
>>> Where does it get the default codeset from? Maybe we could constrain
>>> that to match the database encoding, the way we do for LC_COLLATE/CTYPE?
>
>> LC_CTYPE. In 8.3 and up where we constrain that to match the database
>> encoding, we only have a problem with the C locale.
>
> ... and even if we wanted to fiddle with it, that just moves the problem
> over to finding an LC_CTYPE value that matches the database encoding
> :-(.
>
> Yup, it's a mess. We'd have done this long ago if it were easy.
>
> Could we get away with just unconditionally calling
> bind_textdomain_codeset with *our* canonical spelling of the encoding
> name? If it works, great, and if it doesn't, you get English.
Yeah, that's better than nothing.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2009-03-30 17:52:29 | Re: PQinitSSL broken in some use casesf |
Previous Message | Tom Lane | 2009-03-30 17:46:14 | Re: PQinitSSL broken in some use casesf |