From: | "mark" <dvlhntr(at)gmail(dot)com> |
---|---|
To: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | locales and encodings Oh MY! |
Date: | 2010-11-12 02:31:51 |
Message-ID: | 000001cb8211$c4c91b00$4e5b5100$@com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Gabriele Bartolini | 2010-11-12 07:45:07 | Re: locales and encodings Oh MY! |
Previous Message | Joshua D. Drake | 2010-11-12 01:38:49 | Re: REVOKE ALL ON SCHEMA pg_catalog FROM PUBLIC |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2010-11-12 02:49:44 | Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running |
Previous Message | Bruce Momjian | 2010-11-12 01:54:17 | Re: duplicate connection failure messages |