database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-31 22:04:40 +03:00
Code Activity

Pg_upgrade C comment addition.

Browse Source 
Document why we do the missing new database check during the check
phase.
This commit is contained in:
Bruce Momjian
2011-04-20 05:44:45 -04:00
parent 2b919118c2
commit 0262251c33
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
contrib/pg_upgrade/check.c
View File

@ -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)