Postgres Pro
Downloads
Home   >   mailing lists

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

From Peter Eisentraut
Subject Re: More message encoding woes
Date
Msg-id 200904010016.34667.peter_e@gmx.net
Whole thread Raw
In response to Re: More message encoding woes  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: More message encoding woes  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
On Monday 30 March 2009 20:06:48 Heikki Linnakangas wrote:
> 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.

Why don't we apply the same restriction to the C locale then?

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: More message encoding woes
Next
From: Tom Lane
Date:
Subject: Re: More message encoding woes