DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=from:to:subject:date:message-id:mime-version:content-type
	:content-transfer-encoding:x-mailer:thread-index:content-language
	:x-cr-hashedpuzzle:x-cr-puzzleid;
	b=kVTowT2tW7u86mo+97ytfZghHySCYV4cCjQkZjkvOSN2IZRo/yY2LM8zONVk0EEnGr
	tZJ7UcTiE7+BDfnG1BjNjCq0KOsFf9qO0fdnbupaGEIY9v9USXhMZrG/M1ppHLt1gx4z
	GN/UlByWMXBZOXMFZMgaNqn70Pe6KkCJM6dOw=
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>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AcuCEcJksL5fekTtQ3GNTADJIAhYFw==
Content-Language: en-us

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