diff options
| author | Bruce Momjian | 2011-04-20 09:44:45 +0000 |
|---|---|---|
| committer | Bruce Momjian | 2011-04-20 09:45:31 +0000 |
| commit | 0262251c337ca066d1b1698684784254849b5676 (patch) | |
| tree | 95097d08ef83726a63aec5205d16832dc0613a70 /contrib | |
| parent | 2b919118c2511c7741c21f325d2ca4f270aa3aba (diff) | |
Pg_upgrade C comment addition.
Document why we do the missing new database check during the check
phase.
Diffstat (limited to 'contrib')
| -rw-r--r-- | contrib/pg_upgrade/check.c | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/contrib/pg_upgrade/check.c b/contrib/pg_upgrade/check.c index 173b29a2c5f..d1dc5dbeaac 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) |