| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tim Uckun <timuckun(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [BUGS] BUG #6034: pg_upgrade fails when it should not. |
| Date: | 2011-05-23 01:39:38 |
| Message-ID: | 201105230139.p4N1dcg12343@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Tim Uckun wrote:
> pg_upgrade from 8.4 to 9.0 fails with the following error message.
>
> old and new cluster lc_collate values do not match
>
>
> on 8.4 show lc_collate outputs
> ------------
> en_NZ.utf8
> (1 row)
>
>
> on 9.0 it outputs
> ------------
> en_NZ.UTF8
> (1 row)
>
>
> So the difference seems to be in capitalization. Presumably they are the
> same collation with "different" names so it strikes me as odd that
> pg_upgrade would balk and refuse to upgrade the database.
>
> pg_upgrade should be able to tell that these are the same collations and go
> ahead with the upgrade.
>
> It also should give some indication of how to overcome the problem.
[ Moved to hackers list.]
Interesting. It can be easily fixed in the C code. Does anyone know of
an example where the case of the locale name is significant in
controlling the behavior?
--
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 | Robert Haas | 2011-05-23 02:13:50 | Re: [BUGS] BUG #6034: pg_upgrade fails when it should not. |
| Previous Message | Craig Ringer | 2011-05-23 01:24:07 | Re: BUG #6033: Nonstandard Install Directory Fails |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-05-23 01:54:07 | Re: timezone GUC |
| Previous Message | Robert Haas | 2011-05-23 01:00:59 | Re: timezone GUC |