Hi Tom, Thanks for the reply -- yes, creating the en_US.utf8 locale and using that, fixed all of my problems. Thanks, --Jatinder -----Original Message----- From: Tom Lane [mailto:tgl@xxxxxxxxxxxxx] Sent: 24 February 2005 17:11 To: Jatinder Sangha Cc: pgsql-general@xxxxxxxxxxxxxx Subject: Re: Unicode support problem "Jatinder Sangha" <js@xxxxxxxxxxxxxxxx> 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 ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings
