Holger Klawitter <[EMAIL PROTECTED]> writes:
> So in other words, all databases inside postgres must have the same (or at
> least a compatible) encoding+locale
Yup. strcoll()'s locale setting implicitly assumes a particular
encoding (at least on the platforms I'm familiar with), and so selecting
Hitesh Bagadiya <[EMAIL PROTECTED]> writes:
> We did set the locate to hi_IN at initdb but sorting is not
> working.
You should check that you have selected a database encoding that matches
what the locale expects. Also double-check that you really do have that
locale selected (use pg_controldata
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> You need to make sure you initdb with the right locale, not only
> the right encoding.
So in other words, all databases inside postgres must have the same (or at
least a compatible) encoding+locale in order to allow proper sorting or other
locale d
We did set the locate to hi_IN at initdb but sorting is not
working. One thing is that linux system is running on en_US
locale. Does this makes any difference?
hitesh
--- Tom Lane <[EMAIL PROTECTED]> wrote:
> Hitesh Bagadiya <[EMAIL PROTECTED]> writes:
> > Our database contains Hindi as well as