doc: move HBA reload instructions above the syntax details

Reported-by: John 
Discussion: https://postgr.es/m/165947088723.651.7641196693246068619@wrigleys.postgresql.org

Backpatch-through: master

diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
index 2f1bd6fc8a70a4fe742847048c0017a94c5a4b57..477f70a65d6517b3c40463ae8e92546269f63e10 100644 (file)
--- a/doc/src/sgml/client-auth.sgml
+++ b/doc/src/sgml/client-auth.sgml
@@ -73,6 +73,35 @@
    however; see the  configuration parameter.
   
 
+  
+   The pg_hba.conf file is read on start-up and when
+   the main server process receives a
+   SIGHUPSIGHUP
+   signal. If you edit the file on an
+   active system, you will need to signal the postmaster
+   (using pg_ctl reload, calling the SQL function
+   pg_reload_conf(), or using kill
+   -HUP) to make it re-read the file.
+  
+
+  
+   
+    The preceding statement is not true on Microsoft Windows: there, any
+    changes in the pg_hba.conf file are immediately
+    applied by subsequent new connections.
+   
+  
+
+  
+   The system view
+   pg_hba_file_rules
+   can be helpful for pre-testing changes to the pg_hba.conf
+   file, or for diagnosing problems if loading of the file did not have the
+   desired effects.  Rows in the view with
+   non-null error fields indicate problems in the
+   corresponding lines of the file.
+  
+
   
    The general format of the pg_hba.conf file is
    a set of records, one per line. Blank lines are ignored, as is any
@@ -733,35 +762,6 @@ openssl x509 -in myclient.crt -noout --subject -nameopt RFC2253 | sed "s/^subjec
    range of allowed client IP addresses.
   
 
-  
-   The pg_hba.conf file is read on start-up and when
-   the main server process receives a
-   SIGHUPSIGHUP
-   signal. If you edit the file on an
-   active system, you will need to signal the postmaster
-   (using pg_ctl reload, calling the SQL function
-   pg_reload_conf(), or using kill
-   -HUP) to make it re-read the file.
-  
-
-  
-   
-    The preceding statement is not true on Microsoft Windows: there, any
-    changes in the pg_hba.conf file are immediately
-    applied by subsequent new connections.
-   
-  
-
-  
-   The system view
-   pg_hba_file_rules
-   can be helpful for pre-testing changes to the pg_hba.conf
-   file, or for diagnosing problems if loading of the file did not have the
-   desired effects.  Rows in the view with
-   non-null error fields indicate problems in the
-   corresponding lines of the file.
-  
-
   
    
     To connect to a particular database, a user must not only pass the
@@ -933,6 +933,28 @@ local   db1,db2,@demodbs  all                                   md5
    As for pg_hba.conf, the lines in this file can
    be include directives, following the same rules.
   
+
+  
+   The pg_ident.conf file is read on start-up and
+   when the main server process receives a
+   SIGHUPSIGHUP
+   signal. If you edit the file on an
+   active system, you will need to signal the postmaster
+   (using pg_ctl reload, calling the SQL function
+   pg_reload_conf(), or using kill
+   -HUP) to make it re-read the file.
+  
+
+  
+   The system view
+   pg_ident_file_mappings
+   can be helpful for pre-testing changes to the
+   pg_ident.conf file, or for diagnosing problems if
+   loading of the file did not have the desired effects.  Rows in the view with
+   non-null error fields indicate problems in the
+   corresponding lines of the file.
+  
+
   
    There is no restriction regarding how many database users a given
    operating system user can correspond to, nor vice versa.  Thus, entries
@@ -999,27 +1021,6 @@ mymap   /^(.*)@otherdomain\.com$   guest
    
   
 
-  
-   The pg_ident.conf file is read on start-up and
-   when the main server process receives a
-   SIGHUPSIGHUP
-   signal. If you edit the file on an
-   active system, you will need to signal the postmaster
-   (using pg_ctl reload, calling the SQL function
-   pg_reload_conf(), or using kill
-   -HUP) to make it re-read the file.
-  
-
-  
-   The system view
-   pg_ident_file_mappings
-   can be helpful for pre-testing changes to the
-   pg_ident.conf file, or for diagnosing problems if
-   loading of the file did not have the desired effects.  Rows in the view with
-   non-null error fields indicate problems in the
-   corresponding lines of the file.
-  
-
   
    A pg_ident.conf file that could be used in
    conjunction with the pg_hba.conf file in