Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, 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 15:22:22
Message-ID: 50607AAE.70400@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

On 9/24/12 11:04 AM, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
>> Well, if you run that query on template0 in the old and new cluster, you
>> will see something different in the two of them. Could you have used
>> default in one and a non-dash in the other. Did we change the way we
>> canonicalize the locale between 9.1 and 9.2?
>
> IIRC, we didn't try to canonicalize locale names at all before 9.2.
> That initdb code you're quoting is of fairly recent vintage.

initdb has changed POSIX to C with glibc at least since 8.3. The code
you're quoting is just a refactoring, AFAICT.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Peter Eisentraut 2012-09-24 15:24:04 Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed
Previous Message Bruce Momjian 2012-09-24 15:07:33 Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2012-09-24 15:24:04 Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed
Previous Message Simon Riggs 2012-09-24 15:16:46 Re: DROP INDEX CONCURRENTLY is not really concurrency safe & leaves around undroppable indexes