Re: 9.0 to 9.2 pg_upgrade pain due to collation mismatch

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Henry C(dot)" <henka(at)cityweb(dot)co(dot)za>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: 9.0 to 9.2 pg_upgrade pain due to collation mismatch
Date: 2012-09-12 18:31:19
Message-ID: 750.1347474679@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Henry C." <henka(at)cityweb(dot)co(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Henry C. 2012-09-12 19:05:22 Re: 9.0 to 9.2 pg_upgrade pain due to collation mismatch
Previous Message Alex Lai 2012-09-12 18:26:02 Planner forces seq scan when select without quoting its values