Recommend postmaster stop/start for pg_upgrade.

diff --git a/doc/src/sgml/ref/pg_upgrade.sgml b/doc/src/sgml/ref/pg_upgrade.sgml
index 293a3876386b905e26b97a9606c0db1c25961384..7bb5167d82bc4897a7c43dbbd87170366cad4675 100644 (file)
--- a/doc/src/sgml/ref/pg_upgrade.sgml
+++ b/doc/src/sgml/ref/pg_upgrade.sgml
@@ -1,5 +1,5 @@
 
 
@@ -119,11 +119,26 @@ pg_upgrade [ -f filename ] 
     
    
 
+   
+    
+     Restore your old pg_hba.conf if needed to allow
+     user logins.
+    
+   
+
+   
+    
+     Stop and restart the postmaster.
+    
+   
+
    
     
      Carefully examine the contents of the upgraded
      database.  If you detect problems, you'll need to recover by restoring
      from your full pg_dump backup.
+     You can delete the data.old/ directory when you
+     are satisfied.
     
    
 
@@ -135,14 +150,6 @@ pg_upgrade [ -f filename ] 
     
    
 
-   
-    
-     Restart the postmaster and/or restore your old
-     pg_hba.conf if needed to allow user logins.
-     You can delete the data.old/ directory when you
-     are finished.
-    
-