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 173b29a2c5ff3daad7d52d3b94f6723819aae422..d1dc5dbeaacc0f61812814536cc6c78299fcdc5a 100644 (file)
--- 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)