Unfortunately, it has been discovered that the fix did not correct
upgrades *from* Postgres 8.3. A new fix has been committed for future
releases of Postgres branches 8.4, 9.0, and 9.1. The details are here:
Again, this only affects users who use pg_upgrade *from* Postgres 8.3.
Bruce Momjian <email@example.com> http://momjian.us