Re: [BUGS] BUG #6034: pg_upgrade fails when it should not. - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [BUGS] BUG #6034: pg_upgrade fails when it should not.
Date
Msg-id 201105252147.p4PLlEN13220@momjian.us
Whole thread Raw
In response to Re: [BUGS] BUG #6034: pg_upgrade fails when it should not.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
> > On Wed, May 25, 2011 at 2:13 PM, Bruce Momjian <bruce@momjian.us> wrote:
> >> I thought the problem was that they upgraded the OS and now the encoding
> >> names changed, though they behaved the same. �Is that now what is
> >> happening? �Can they supply the values with different cases?
> 
> > Oh, hmm.  I don't know.
> 
> The original complaint wasn't too clear.  But I agree with Robert that
> case-insensitive comparison is about as far as it seems safe to go in
> trying to allow for variant spellings of locale names.  I would think
> that a platform that randomly whacks such names around is going to find
> a whole lot of software breaking, not only Postgres.

Agreed.  Unless an expert shows up and can tell us exactly how the
naming works, we have gone as far as we can go.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Nested CASE-WHEN scoping
Next
From: Tom Lane
Date:
Subject: Re: [ADMIN] pg_class reltuples/relpages not updated by autovacuum/vacuum