Thanks All.
I have got a solution. When we give initdb, given it with --locale=C and created database with 'UNICODE'.
This one worked. as of now everything seems to be working. I hope , there wont be any issues, please let me know, if you have any suggestions.
Thanks,
Prakash.
From: Tom Lane <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] (Tomas Zerolo)
CC: Prakash Nair <[EMAIL PROTECTED]>, pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #2071: ERROR: invalid multibyte character for locale
Date: Sat, 26 Nov 2005 11:21:11 -0500
[EMAIL PROTECTED] (Tomas Zerolo) writes:
> - What is the nevironment of the server process? That is: what does the
> shell command 'locale' say when it is issued in the same environment
> as the server starts? (that is not necessarily the environment you get
> if you start a shell!). Try, e.g. putting ''export LANG=us_US.UTF-8''
> just before the server is called (typically in /etc/init.d/postgresql
> or thereabout.
In recent PG versions you can do SHOW LC_COLLATE and/or SHOW LC_CTYPE
to verify the locale settings the server is using. Note that these are
locked down based on the environment seen by initdb --- you can't change
them just by inserting an environment setting into the postmaster start
script.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
