From: | Jamie Lawrence <jal(at)jal(dot)org> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | Different encodings in different DBs in same cluster |
Date: | 2005-07-21 18:32:24 |
Message-ID: | 20050721183224.GA19811@clueinc.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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(at)jal(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Ricky Sutanto | 2005-07-22 03:13:12 | Counting Row |
Previous Message | Michael Fuhr | 2005-07-21 16:23:03 | Re: Are long term never commited SELECT statements are a problem? |