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 750.1347474679@sss.pgh.pa.us
Whole thread Raw
In response to 9.0 to 9.2 pg_upgrade pain due to collation mismatch  ("Henry C." <henka@cityweb.co.za>)
Responses Re: 9.0 to 9.2 pg_upgrade pain due to collation mismatch  ("Henry C." <henka@cityweb.co.za>)
Re: 9.0 to 9.2 pg_upgrade pain due to collation mismatch  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-general
"Henry C." <henka@cityweb.co.za> writes:
> 2.  My 9.0 (old) db is using encoding/Collation/Ctype:
> SQL_ASCII/POSIX/POSIX, and for the life of me I cannot initdb the new
> (9.2) data/ folder to the same to ensure pg_upgrade works (currently keep
> getting "old and new cluster lc_collate values do not match" error).

"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?

Anyway, simplest fix seems to be to update the 9.0 installation's
pg_database to say "C" in those entries.

            regards, tom lane


pgsql-general by date:

Previous
From: Devrim GÜNDÜZ
Date:
Subject: Re: 9.0 to 9.2 pg_upgrade pain due to collation mismatch
Next
From: "Henry C."
Date:
Subject: Re: 9.0 to 9.2 pg_upgrade pain due to collation mismatch