From: Peter Eisentraut <peter_e@gmx.net>
Date: Tue, 4 Nov 2014 21:10:58 +0000 (-0500)
Subject: doc: Move misplaced paragraph
X-Git-Tag: REL9_5_ALPHA1~1268
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=e809fa2c80e051ed49a3ed2206dc055a10d588a4;p=postgresql

doc: Move misplaced paragraph
---

diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml
index 5f6ad6b5fb..705bddb951 100644
--- a/doc/src/sgml/protocol.sgml
+++ b/doc/src/sgml/protocol.sgml
@@ -1483,6 +1483,14 @@ The commands accepted in walsender mode are:
       message, and then starts to stream WAL to the frontend.
      </para>
 
+     <para>
+      If a slot's name is provided
+      via <replaceable class="parameter">slot_name</>, it will be updated
+      as replication progresses so that the server knows which WAL segments,
+      and if <varname>hot_standby_feedback</> is on which transactions,
+      are still needed by the standby.
+     </para>
+
      <para>
       If the client requests a timeline that's not the latest, but is part of
       the history of the server, the server will stream all the WAL on that
@@ -1514,14 +1522,6 @@ The commands accepted in walsender mode are:
       client contains a message of one of the following formats:
      </para>
 
-     <para>
-      If a slot's name is provided
-      via <replaceable class="parameter">slot_name</>, it will be updated
-      as replication progresses so that the server knows which WAL segments -
-      and if <varname>hot_standby_feedback</> is on which transactions -
-      are still needed by the standby.
-     </para>
-
      <para>
       <variablelist>
       <varlistentry>