Commit 0262251c authored by Bruce Momjian's avatar Bruce Momjian

Pg_upgrade C comment addition.

Document why we do the missing new database check during the check
phase.
parent 2b919118
...@@ -372,7 +372,9 @@ check_new_cluster_is_empty(void) ...@@ -372,7 +372,9 @@ check_new_cluster_is_empty(void)
* the new cluster has a 'postgres' database, the number of databases * the new cluster has a 'postgres' database, the number of databases
* will not match. We actually could upgrade such a setup, but it would * 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 * 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 static void
check_old_cluster_has_new_cluster_dbs(void) check_old_cluster_has_new_cluster_dbs(void)
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment