@@ -19,10 +19,10 @@ version must be used.
19191) Back up your existing data directory, preferably by making a complete
2020dump with pg_dumpall.
2121.LP
22- 2) Copy the programpgsql /contrib/pg_upgrade/pg_upgrade from the current
23- PostgreSQL distributioninto somewherein your path.
22+ 2) Copy the program\fI pgsql /contrib/pg_upgrade/pg_upgrade\fP
23+ PostgreSQL distribution somewhereinto your path.
2424.LP
25- 3) Change your working directory to the
25+ 3) Change your working directory to the pgsql main directory, and type:
2626.LP
2727.B $ pg_upgrade -1
2828.sp
@@ -40,18 +40,18 @@ to install the new binaries.
4040.br
4141.B $ make install
4242.sp
43- to install thepg_resetxlog utility which is needed by
43+ to install the\fI pg_resetxlog \fP
4444pg_upgrade.
4545.LP
46466) Run initdb to create a new template1 database containing the system
4747tables for the new release. Make sure you use settings similar to those
4848used in your previous version.
4949.LP
50- 7) Start the newpostmaster. (Note: it is critical that no users connect
50+ 7) Start the new\fI postmaster. \fP
5151to the server until the upgrade is complete. You may wish to start the
52- postmaster without -iand/ or alter pg_hba.conf temporarily.)
52+ postmaster without -i or alter pg_hba.conf temporarily.)
5353.LP
54- 8) Change your working directory to the
54+ 8) Change your working directory to the pgsql main directory, and type:
5555.LP
5656.B $ pg_upgrade -2
5757.sp
@@ -61,15 +61,15 @@ but with no data. It will then physically move the data files
6161containing non-system tables and indexes into the proper
6262subdirectories.
6363.LP
64- 9) Restore your oldpg_hba .conf if needed to allow user logins.
64+ 9) Restore your old\fI pg_hba .conf\fP
6565.sp
6666.LP
676710) Carefully examine the contents of the upgraded databases. If you
6868detect problems, you'll need to recover by restoring from your full
69- pg_dump backup. You can delete thepg_upgrade_info/ directory when you
69+ pg_dump backup. You can delete the\fI pg_upgrade_info/ \fP
7070are satisfied.
7171.LP
7272The upgraded databases will be in an un-vacuumed state. You will
73- probably want to run aVACUUM ANALYZE before beginning production work.
73+ probably want to run a\fI VACUUM ANALYZE \fB before beginning production work.
7474.SH SEE ALSO
7575initdb(1), postmaster(1), pg_dump(1), pg_dumpall(1), vacuumdb(1)