Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Use <substeps> in pg_upgrade's procedure
authorAlvaro Herrera <alvherre@alvh.no-ip.org>
Tue, 1 Sep 2015 17:58:28 +0000 (14:58 -0300)
committerAlvaro Herrera <alvherre@alvh.no-ip.org>
Tue, 1 Sep 2015 18:12:35 +0000 (15:12 -0300)
For clarity, so that the substeps are not numbered identically to the
outer procedure's steps.

Per report from Andy Colson in
http://www.postgresql.org/message-id/55D789B5.7040308@squeakycode.net

doc/src/sgml/ref/pgupgrade.sgml

index 072d5f46eb22ad7e47c6ced5c3350dabc35b5d25..ebc0d58887e1b977357d7a26e6785f1a15fed387 100644 (file)
@@ -407,7 +407,7 @@ pg_upgrade.exe
      upgrade them (before starting any servers):
     </para>
 
-    <procedure>
+    <substeps>
 
      <step>
       <title>Install the new PostgreSQL binaries on standby servers</title>
@@ -522,7 +522,7 @@ rsync --archive --delete --hard-links --size-only old_pgdata new_pgdata remote_d
       </para>
      </step>
 
-    </procedure>
+    </substeps>
 
    </step>