Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit0262251

Browse files
committed
Pg_upgrade C comment addition.
Document why we do the missing new database check during the checkphase.
1 parent2b91911 commit0262251

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

‎contrib/pg_upgrade/check.c

Lines changed: 3 additions & 1 deletion
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
staticvoid
378380
check_old_cluster_has_new_cluster_dbs(void)

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp