Re: LC_COLLATE and pg_upgrade - Mailing list pgsql-admin

From Bernhard Schrader
Subject Re: LC_COLLATE and pg_upgrade
Date
Msg-id 1297858458.2367.11.camel@schrader-laptop
Whole thread Raw
In response to Re: LC_COLLATE and pg_upgrade  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: LC_COLLATE and pg_upgrade
List pgsql-admin
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.
>
>
>




pgsql-admin by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: LC_COLLATE and pg_upgrade
Next
From: Greg Smith
Date:
Subject: Re: Moving the data directory