aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlvaro Herrera <alvherre@alvh.no-ip.org>2015-09-01 14:58:28 -0300
committerAlvaro Herrera <alvherre@alvh.no-ip.org>2015-09-01 15:12:35 -0300
commitc1564b3928e527c799bd41c2c80c4d6851bb5e15 (patch)
tree426c3314a21a785e92b6e6c484a3d130c98ef282
parent06502185d8352258560b7fad82571d159dff8658 (diff)
downloadpostgresql-c1564b3928e527c799bd41c2c80c4d6851bb5e15.tar.gz
postgresql-c1564b3928e527c799bd41c2c80c4d6851bb5e15.zip
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
-rw-r--r--doc/src/sgml/ref/pgupgrade.sgml4
1 files 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>