The attached, applied patch adds a check to throw a pg_upgrade error
during the check phase, rather than during the post-check upgrade phase.
Specifically, if someone removes the 'postgres' database from the old
cluster and the new cluster has a 'postgres' database, the number of
databases will not match. We actually could upgrade such a setup, but
it would violate the 1-to-1 mapping of database counts, so we throw an
Previously they got an error during the upgrade, and not at the check
stage; PG 9.0.4 does the same.
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
+ It's impossible for everything to be true. +
pgsql-hackers by date
|Next:||From: Hiroshi Inoue||Date: 2011-04-20 01:42:35|
|Subject: Re: [HACKERS] Re: pgsql: setlocale() on Windows doesn't
work correctly if the locale name|
|Previous:||From: Tom Lane||Date: 2011-04-20 00:37:12|
|Subject: Re: Insufficient description in collation mismatch error |