| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| 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 18:57:27 |
| Message-ID: | 201105231857.p4NIvRh13495@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Robert Haas wrote:
> 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?
Well, if we remove the check then people could easily get broken
upgrades by upgrading to a server with a different locale. A Google
search seems to indicate the locale names are case-sensitive so I am
thinking the problem is that the user didn't have exact locales, and
needs that to use pg_upgrade.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martin A. Brooks | 2011-05-23 18:58:27 | Re: BUG #6028: age() function output contracts "months", but not any other units. |
| Previous Message | Tom Lane | 2011-05-23 18:50:59 | Re: BUG #6028: age() function output contracts "months", but not any other units. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-05-23 19:01:40 | Re: Identifying no-op length coercions |
| Previous Message | Robert Haas | 2011-05-23 18:53:01 | Re: Identifying no-op length coercions |