Re: 9.0 to 9.2 pg_upgrade pain due to collation mismatch - Mailing list pgsql-general

From Tom Lane
Subject Re: 9.0 to 9.2 pg_upgrade pain due to collation mismatch
Date
Msg-id 23341.1347574826@sss.pgh.pa.us
Whole thread Raw
In response to Re: 9.0 to 9.2 pg_upgrade pain due to collation mismatch  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-general
Peter Eisentraut <peter_e@gmx.net> writes:
> On 9/12/12 2:31 PM, Tom Lane wrote:
>> "C" is the official name of that locale.  Not sure how you got it to say
>> "POSIX" ... maybe we didn't have normalization of the locale name back
>> then?

> Says who?

Says setlocale(), at least on the Fedora machine I just checked.
The reason I see this:

$ initdb --locale=POSIX
The files belonging to this database system will be owned by user "tgl".
This user must also own the server process.

The database cluster will be initialized with locale "C".
The default database encoding has accordingly been set to "SQL_ASCII".
The default text search configuration will be set to "english".

is that setlocale is returning "C" as the canonical name of the locale.

            regards, tom lane


pgsql-general by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Fixing or diagnosing Canceled on identification as a pivot, during write
Next
From: Edson Richter
Date:
Subject: Re: Compressed binary field