Subject: Re: LC_COLLATE and pg_upgrade
From: Bernhard Schrader <bernhard.schrader@innogames.de>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-admin@postgresql.org
In-Reply-To: <1297857285.8578.1.camel@fsopti579.F-Secure.com>
References: <1297357018.2340.10.camel@schrader-laptop>
	<1297689493.2293.5.camel@schrader-laptop>
	<1297857285.8578.1.camel@fsopti579.F-Secure.com>
Content-Type: text/plain; charset="UTF-8"
Organization: Innogames GmbH
Date: Wed, 16 Feb 2011 13:14:18 +0100
Message-ID: <1297858458.2367.11.camel@schrader-laptop>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit

If i reinitialize the database cluster, won't i have to pg_dump restore
my data? In this case the downtime would be to big. Therefore I'm
searching for a faster way. 

utf8 and UTF-8, should be the same in my opinion, so i think there must
be a way to just change this value, so that pg_upgrade can do his work,
or is this impossible?

regards

Am Mittwoch, den 16.02.2011, 13:54 +0200 schrieb Peter Eisentraut:
> On mån, 2011-02-14 at 14:18 +0100, Bernhard Schrader wrote:
> > As far as I read right now, LC_COLLATE is a read_only variable which
> > is used while initdb. But why does the pg_upgrade script doesn't see
> > that utf8 and UTF-8 are the same? Is it just a string compare? 
> 
> Why don't you just reinitialize your new database cluster with the same
> locale spelling as the old one?
> 
> Your points are valid, but unfortunately difficult to handle in the
> general case.
> 
> 
>