From: mark <dvlhntr@gmail.com>
To: pgsql-admin@postgresql.org
Subject: locales and encodings Oh MY!
Date: Thu, 11 Nov 2010 19:31:51 -0700
Message-ID: <000001cb8211$c4c91b00$4e5b5100$@com> (raw)
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: dvlhntr@gmail.com
Subject: Re: locales and encodings Oh MY!
In-Reply-To: <000001cb8211$c4c91b00$4e5b5100$@com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox