On Sun, May 22, 2011 at 9:39 PM, Bruce Momjian <br...@momjian.us> wrote: > 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?
Uh, are we talking about locale, or collation? Because if it's collation, that seems certain to affect index contents. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
