Date: Thu, 21 Jul 2005 14:32:24 -0400
From: Jamie Lawrence <jal@jal.org>
To: pgsql-sql@postgresql.org
Subject: Different encodings in different DBs in same cluster
Message-ID: <20050721183224.GA19811@clueinc.net>
Mail-Followup-To: pgsql-sql@postgresql.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
Organization: clue inc


Hi All, 

I was going through the docs for Postgres 8 for info on setting the
character set (to UTF8). In the docs here:

http://www.postgresql.org/docs/8.0/interactive/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED

I see:

   Since these locale settings are frozen by initdb, the apparent
   flexibility to use different encodings in different databases of a
   cluster is more theoretical than real. It is likely that these
   mechanisms will be revisited in future versions of PostgreSQL.
  
   One way to use multiple encodings safely is to set the locale
   to C or POSIX during initdb, thus disabling any real locale
   awareness. 

Does anyone know what "more theoretical than real" mean in this context?
If I set the locale to C, is it going to work correctly with UTF8
encoded data?

Thanks,

-j

-- 
Jamie Lawrence                                        jal@jal.org
It's strange to hear people like Gordon Liddy talking about morality. 
He hasn't been out of jail all that long.
   - Ben Bradlee