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

From Robert Haas
Subject Re: [BUGS] BUG #6034: pg_upgrade fails when it should not.
Date
Msg-id BANLkTimDXBRXxr0SiBU9AQCm1_Eb8mye-g@mail.gmail.com
Whole thread Raw
In response to Re: [BUGS] BUG #6034: pg_upgrade fails when it should not.  (Bruce Momjian <bruce@momjian.us>)
Responses Re: [BUGS] BUG #6034: pg_upgrade fails when it should not.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, May 25, 2011 at 2:13 PM, Bruce Momjian <bruce@momjian.us> wrote:
> Alvaro Herrera wrote:
>> Excerpts from Robert Haas's message of mié may 25 13:33:41 -0400 2011:
>> > On Wed, May 25, 2011 at 1:22 PM, Bruce Momjian <bruce@momjian.us> wrote:
>>
>> > > I can easily remove dashes before the compare if people like that idea
>> > > --- I think you could argue that a dash is not significant, unless "ab-c"
>> > > and "a-bc" are different locales.
>> >
>> > I think the more we mush that string around, the more chance we have
>> > of breaking something.  What's wrong with insisting that people set
>> > the value to the same thing?  Like, really the same?
>>
>> No objection here to that idea.
>
> 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.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Re: The way to know whether the standby has caught up with the master
Next
From: Simon Riggs
Date:
Subject: Re: use less space in xl_xact_commit patch