Re: More message encoding woes - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: More message encoding woes
Date
Msg-id 49D0FC28.4040404@enterprisedb.com
Whole thread Raw
In response to Re: More message encoding woes  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: More message encoding woes  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: More message encoding woes  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
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.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: More message encoding woes
Next
From: Tom Lane
Date:
Subject: Re: Unexpected Result in Windowing