1
0
mirror of https://github.com/postgres/postgres.git synced 2025-08-09 17:03:00 +03:00

In pg_upgrade, only lock the old cluster if link mode is used, and do it

right after we restore the schema (a common failure point), and right
before we do the link operation.

Per suggesgtions from Robert and ^!C^!^@lvaro
This commit is contained in:
Bruce Momjian
2012-03-05 21:19:54 -05:00
parent 6b289942bf
commit 2127aac6ef
5 changed files with 37 additions and 35 deletions

View File

@@ -148,9 +148,8 @@ report_clusters_compatible(void)
}
pg_log(PG_REPORT, "\n"
"If pg_upgrade fails after this point, you must re-initdb the new cluster\n"
"before continuing. You will also need to remove the \".old\" suffix from\n"
"%s/global/pg_control.old.\n", old_cluster.pgdata);
"If pg_upgrade fails after this point, you must re-initdb the\n"
"new cluster before continuing.\n");
}
@@ -198,8 +197,8 @@ output_completion_banner(char *deletion_script_file_name)
/* Did we copy the free space files? */
if (GET_MAJOR_VERSION(old_cluster.major_version) >= 804)
pg_log(PG_REPORT,
"Optimizer statistics are not transferred by pg_upgrade so consider\n"
"running:\n"
"Optimizer statistics are not transferred by pg_upgrade so\n"
"consider running:\n"
" vacuumdb --all --analyze-only\n"
"on the newly-upgraded cluster.\n\n");
else