locales and encodings Oh MY! - Mailing list pgsql-admin

From mark
Subject locales and encodings Oh MY!
Date
Msg-id 000001cb8211$c4c91b00$4e5b5100$@com
Whole thread Raw
Responses Re: locales and encodings Oh MY!
List pgsql-admin
Hi all,

So today while I investigating some slow queries I found out that some time
ago some of our databases (due, innocently I suspect, to upgrades or
hardware migrations) are now not using C as lc_ctype. And why some 'things'
got a lot slower...

To correct this problem it seems like I am going to have to do a dump,
intidb, then restore.  (or add some new indexes and eat the extra overhead).
Unless someone knows something I don't about changing ctype and collation
with some sleight of hand (if you do I am very interested)


I have listed what I think I will be doing with regards to initdb. if anyone
sees problems with the following mixture during my dump -> init-> restore I
would be most keen in hearing about it.



initdb /path/to/data/dir --lc_ctype=C --lc_collation=C
--lc_message=en_US.UTF8 --lc_monetary=en_US.UTF8 --lc_numeric=en_US.UTF8
--lc_time=en_US.UTF8 -E UTF8




Thank you,

Mark


pgsql-admin by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: REVOKE ALL ON SCHEMA pg_catalog FROM PUBLIC
Next
From: Gabriele Bartolini
Date:
Subject: Re: locales and encodings Oh MY!