From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Jatinder Sangha" <js(at)coalitiondev(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Unicode support problem |
Date: | 2005-02-24 17:11:09 |
Message-ID: | 25769.1109265069@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Jatinder Sangha" <js(at)coalitiondev(dot)com> writes:
> I've setup the postgres database as follows:
> LANG=C
> initdb -E UNICODE
> createdb -E UNICODE
> I have tried setting locale/lc_ctype to C, POSIX, iso_8859_1, all kinds
> of things, and nothing seems to fix it.
You can't just pick random combinations of locale and database encoding.
Any given locale setting implies a character set encoding, and you have
to use that same encoding as the database encoding; at least if you want
encoding-dependent operations such as upper()/lower() to work. The
locale you want for Unicode (UTF8) may be named something like
"en_US.utf8". Try "locale -a" to get a list of supported locales.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Terry Lee Tucker | 2005-02-24 17:49:01 | Re: Questions regarding notify processing. |
Previous Message | Tom Lane | 2005-02-24 17:06:10 | Re: Questions regarding notify processing. |