postgres.git / summary / log / commit / refs

commit    9646d2fd62a444ab4502e49dfe3cbf9d7350c5e2
Author:   Alvaro Herrera <alvherre@alvh.no-ip.org>
Date:     Tue Sep 01 17:58:28 2015 +0000
First released in: 9.6.0, 9.5.0

    Use <substeps> in pg_upgrade's procedure
    
    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 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml
index 072d5f46eb2..ebc0d58887e 100644
--- a/doc/src/sgml/ref/pgupgrade.sgml
+++ b/doc/src/sgml/ref/pgupgrade.sgml
@@ -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>
 


[parent: 123c9d2fc1fe]