From: Bruce Momjian <bruce@momjian.us>
Date: Wed, 20 Apr 2011 09:44:45 +0000 (-0400)
Subject: Pg_upgrade C comment addition.
X-Git-Tag: REL9_1_BETA1~58
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=0262251c337ca066d1b1698684784254849b5676;p=postgresql

Pg_upgrade C comment addition.

Document why we do the missing new database check during the check
phase.
---

diff --git a/contrib/pg_upgrade/check.c b/contrib/pg_upgrade/check.c
index 173b29a2c5..d1dc5dbeaa 100644
--- a/contrib/pg_upgrade/check.c
+++ b/contrib/pg_upgrade/check.c
@@ -372,7 +372,9 @@ check_new_cluster_is_empty(void)
  *	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 error
- *	instead.
+ *	instead.  We would detect this as a database count mismatch during
+ *	upgrade, but we want to detect it during the check phase and report
+ *	the database name.
  */
 static void
 check_old_cluster_has_new_cluster_dbs(void)