Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 0262251

Browse files
committed
Pg_upgrade C comment addition.
Document why we do the missing new database check during the check phase.
1 parent 2b91911 commit 0262251

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

contrib/pg_upgrade/check.c

+3-1
Original file line numberDiff line numberDiff line change
@@ -372,7 +372,9 @@ check_new_cluster_is_empty(void)
372372
* the new cluster has a 'postgres' database, the number of databases
373373
* will not match. We actually could upgrade such a setup, but it would
374374
* violate the 1-to-1 mapping of database counts, so we throw an error
375-
* instead.
375+
* instead. We would detect this as a database count mismatch during
376+
* upgrade, but we want to detect it during the check phase and report
377+
* the database name.
376378
*/
377379
static void
378380
check_old_cluster_has_new_cluster_dbs(void)

0 commit comments

Comments
 (0)