10000 Use <substeps> in pg_upgrade's procedure · postgrespro/postgres_cluster@9646d2f · GitHub
[go: up one dir, main page]
Skip to content

Commit 9646d2f

Browse files
alvherrealvherre
committed
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
1 parent 123c9d2 commit 9646d2f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

‎doc/src/sgml/ref/pgupgrade.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -407,7 +407,7 @@ pg_upgrade.exe
407407
upgrade them (before starting any servers):
408408
</para>
409409

410-
<procedure>
410+
<substeps>
411411

412412
<step>
413413
<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
522522
</para>
523523
</step>
524524

525-
</procedure>
525+
</substeps>
526526

527527
</step>
528528

0 commit comments

Comments
 (0)
0