Re: encoding and LC_COLLATE - Mailing list pgsql-general

From LPlateAndy
Subject Re: encoding and LC_COLLATE
Date
Msg-id 1321273268503-4990605.post@n5.nabble.com
Whole thread Raw
In response to encoding and LC_COLLATE  (LPlateAndy <andy@centremaps.co.uk>)
List pgsql-general
Hi,

In response to my own question i have now read the following:

http://stackoverflow.com/questions/6579621/lc-collate-and-lc-ctype-suport-for-utf-8-in-postgresql

It seems to show that apart from a complete reinstall i should just use a
Locale of C (as i'm on Windows and POSIX wont work).

This is a bit of an issue as i wanted to use a PostGIS template table with
all of the functions assigned but i can only create a new database with
Locale C by setting the template as template_0.

So, any info on being able to reset the value on an existing table would be
much appreciate - otherwise i'll get on to Postgres 9.1 and start reloading
all the data...

Thanks

Andy

--
View this message in context: http://postgresql.1045698.n5.nabble.com/encoding-and-LC-COLLATE-tp4990415p4990605.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

pgsql-general by date:

Previous
From: LPlateAndy
Date:
Subject: encoding and LC_COLLATE
Next
From: LPlateAndy
Date:
Subject: issue with delimiter in field during COPY