Re: [BUGS] BUG #6034: pg_upgrade fails when it should not.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tim Uckun <timuckun(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [BUGS] BUG #6034: pg_upgrade fails when it should not.
Date: 2011-05-23 16:53:29
Message-ID: BANLkTi=PgvZ==Yj=Sf8Yp0HT=ygn75_-sg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Mon, May 23, 2011 at 8:26 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Sorry, I was unclear.  The question is whether the case of _name_ of the
> locale is significant, meaning can you have two locale names that differ
> only by case and behave differently?

That would seem surprising to me, but I really have no idea.

There's the other direction, too: two locales that vary by something
more than case, but still have identical behavior. Maybe we just
decide not to worry about that, but then why worry about this?

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2011-05-23 16:54:26 Re: BUG #6035: server crash when executing recursive query (trying to allocate 16 Exabyte memory)
Previous Message Tom Lane 2011-05-23 15:36:38 Re: Seg-fault in format(text)

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-05-23 17:21:10 Re: Identifying no-op length coercions
Previous Message Robert Haas 2011-05-23 16:49:31 Re: Identifying no-op length coercions