Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Rural Hunter <ruralhunter(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed
Date: 2012-09-24 14:13:45
Message-ID: 14327.1348496025@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
>>> I can confirm that pg_upgrade does case-insensitive comparisons of
>>> encoding/locale names:

> Or we could just remove dashes from the name before comparisons.

That would merely move the breakage somewhere else. I think you are
already assuming far too much about the OS' interpretation of locale
names by assuming they are case-insensitive. Assuming that dashes
aren't significant seems 100% wrong.

FWIW, what I found out last time I touched this code is that on many
systems setlocale doesn't bother to return a canonicalized spelling;
it just gives back the string you gave it. It might be worth doing
what Peter suggests, just to be consistent with what we are doing
elsewhere, but I'm not sure how much it will help.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Bruce Momjian 2012-09-24 14:26:59 Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed
Previous Message Rural Hunter 2012-09-24 13:59:02 Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2012-09-24 14:17:53 Re: pg_reorg in core?
Previous Message Rural Hunter 2012-09-24 13:59:02 Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed