On Sat, Mar 7, 2009 at 3:25 PM, Jon Burgess <[email protected]> wrote: > > I believe this is the only solution. It it explained at (1) and in the > initdb manual page > > initdb initializes the database cluster’s default locale and character > set encoding. The collation order (LC_COLLATE) and character set > classes (LC_CTYPE, e.g. upper, lower, digit) are fixed for all databases and > cannot be changed. Collation orders other than C or POSIX also > have a performance penalty. For these reasons it is important to choose > the right locale when running initdb. The remaining locale cate- > gories can be changed later when the server is started. All server locale > values (lc_*) can be displayed via SHOW ALL. More details can be > found in in the documentation. > > On debian derived systems, the initdb command is wrapped by the > pg_createcluster script. > > Jon > > > [1] http://www.postgresql.org/docs/8.3/static/multibyte.html > > >
Thanks...then i think it'll be better to do a local pgsql install instead of doing changes globally. Tim/chippy told that can be an option and i think it'll work out well :) -- best Arindam _______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
