11<!--
2- $Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pg_upgrade.sgml,v 1.7 1999/09/2803:41:35 momjian Exp $
2+ $Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pg_upgrade.sgml,v 1.8 1999/09/2815:59:10 momjian Exp $
33Postgres documentation
44-->
55
@@ -119,11 +119,26 @@ pg_upgrade [ -f <replaceable class="parameter">filename</replaceable> ] <replace
119119 </para>
120120 </step>
121121
122+ <step performance="required">
123+ <para>
124+ Restore your old <filename>pg_hba.conf</filename> if needed to allow
125+ user logins.
126+ </para>
127+ </step>
128+
129+ <step performance="required">
130+ <para>
131+ Stop and restart the postmaster.
132+ </para>
133+ </step>
134+
122135 <step performance="required">
123136 <para>
124137 <emphasis>Carefully</emphasis> examine the contents of the upgraded
125138 database. If you detect problems, you'll need to recover by restoring
126139 from your full pg_dump backup.
140+ You can delete the <filename>data.old/</filename> directory when you
141+ are satisfied.
127142 </para>
128143 </step>
129144
@@ -135,14 +150,6 @@ pg_upgrade [ -f <replaceable class="parameter">filename</replaceable> ] <replace
135150 </para>
136151 </step>
137152
138- <step performance="required">
139- <para>
140- Restart the postmaster and/or restore your old
141- <filename>pg_hba.conf</filename> if needed to allow user logins.
142- You can delete the <filename>data.old/</filename> directory when you
143- are finished.
144- </para>
145- </step>
146153 </procedure>
147154 </refsect1>
148155</refentry>