1
0
mirror of https://github.com/postgres/postgres.git synced 2025-07-30 11:03:19 +03:00

Use "upgrade" in preference over "migrate" in pg_upgrade messages and

documentation.  (Many were left over from the old pg_migrator naming.)
This commit is contained in:
Bruce Momjian
2010-12-15 07:11:31 -05:00
parent 34c70c7ac4
commit 16b5e08dec
10 changed files with 43 additions and 44 deletions

View File

@ -26,7 +26,7 @@ static void putenv2(const char *var, const char *val);
* and then pipe its output. With little string parsing we get the
* pg_control data. pg_resetxlog cannot be run while the server is running
* so we use pg_controldata; pg_controldata doesn't provide all the fields
* we need to actually perform the migration, but it provides enough for
* we need to actually perform the upgrade, but it provides enough for
* check mode. We do not implement pg_resetxlog -n because it is hard to
* return valid xid data for a running server.
*/
@ -505,8 +505,8 @@ check_control_data(ControlData *oldctrl,
"\nOld and new pg_controldata date/time storage types do not match.\n");
/*
* This is a common 8.3 -> 8.4 migration problem, so we are more
* verboase
* This is a common 8.3 -> 8.4 upgrade problem, so we are more
* verbose
*/
pg_log(PG_FATAL,
"You will need to rebuild the new server with configure\n"