Doc improvements.
This commit is contained in:
parent
15ca0a502c
commit
0451c09fd6
|
@ -19,10 +19,10 @@ version must be used.
|
||||||
1) Back up your existing data directory, preferably by making a complete
|
1) Back up your existing data directory, preferably by making a complete
|
||||||
dump with pg_dumpall.
|
dump with pg_dumpall.
|
||||||
.LP
|
.LP
|
||||||
2) Copy the program pgsql/contrib/pg_upgrade/pg_upgrade from the current
|
2) Copy the program \fIpgsql/contrib/pg_upgrade/pg_upgrade\fP from the current
|
||||||
PostgreSQL distribution into somewhere in your path.
|
PostgreSQL distribution somewhere into your path.
|
||||||
.LP
|
.LP
|
||||||
3) Change your working directory to the pgsql main directory, and type:
|
3) Change your working directory to the pgsql main directory, and type:
|
||||||
.LP
|
.LP
|
||||||
.B $ pg_upgrade -1
|
.B $ pg_upgrade -1
|
||||||
.sp
|
.sp
|
||||||
|
@ -40,18 +40,18 @@ to install the new binaries.
|
||||||
.br
|
.br
|
||||||
.B $ make install
|
.B $ make install
|
||||||
.sp
|
.sp
|
||||||
to install the pg_resetxlog utility which is needed by
|
to install the \fIpg_resetxlog\fP utility which is needed by
|
||||||
pg_upgrade.
|
pg_upgrade.
|
||||||
.LP
|
.LP
|
||||||
6) Run initdb to create a new template1 database containing the system
|
6) Run initdb to create a new template1 database containing the system
|
||||||
tables for the new release. Make sure you use settings similar to those
|
tables for the new release. Make sure you use settings similar to those
|
||||||
used in your previous version.
|
used in your previous version.
|
||||||
.LP
|
.LP
|
||||||
7) Start the new postmaster. (Note: it is critical that no users connect
|
7) Start the new \fIpostmaster.\fP (Note: it is critical that no users connect
|
||||||
to the server until the upgrade is complete. You may wish to start the
|
to the server until the upgrade is complete. You may wish to start the
|
||||||
postmaster without -i and/or alter pg_hba.conf temporarily.)
|
postmaster without -i or alter pg_hba.conf temporarily.)
|
||||||
.LP
|
.LP
|
||||||
8) Change your working directory to the pgsql main directory, and type:
|
8) Change your working directory to the pgsql main directory, and type:
|
||||||
.LP
|
.LP
|
||||||
.B $ pg_upgrade -2
|
.B $ pg_upgrade -2
|
||||||
.sp
|
.sp
|
||||||
|
@ -61,15 +61,15 @@ but with no data. It will then physically move the data files
|
||||||
containing non-system tables and indexes into the proper
|
containing non-system tables and indexes into the proper
|
||||||
subdirectories.
|
subdirectories.
|
||||||
.LP
|
.LP
|
||||||
9) Restore your old pg_hba.conf if needed to allow user logins.
|
9) Restore your old \fIpg_hba.conf\fP if needed to allow user logins.
|
||||||
.sp
|
.sp
|
||||||
.LP
|
.LP
|
||||||
10) Carefully examine the contents of the upgraded databases. If you
|
10) Carefully examine the contents of the upgraded databases. If you
|
||||||
detect problems, you'll need to recover by restoring from your full
|
detect problems, you'll need to recover by restoring from your full
|
||||||
pg_dump backup. You can delete the pg_upgrade_info/ directory when you
|
pg_dump backup. You can delete the \fIpg_upgrade_info/\fP directory when you
|
||||||
are satisfied.
|
are satisfied.
|
||||||
.LP
|
.LP
|
||||||
The upgraded databases will be in an un-vacuumed state. You will
|
The upgraded databases will be in an un-vacuumed state. You will
|
||||||
probably want to run a VACUUM ANALYZE before beginning production work.
|
probably want to run a \fIVACUUM ANALYZE\fB before beginning production work.
|
||||||
.SH SEE ALSO
|
.SH SEE ALSO
|
||||||
initdb(1), postmaster(1), pg_dump(1), pg_dumpall(1), vacuumdb(1)
|
initdb(1), postmaster(1), pg_dump(1), pg_dumpall(1), vacuumdb(1)
|
||||||
|
|
Loading…
Reference in a new issue