Fix some trailing whitespace in documentation files

Author: petere

doc/src/sgml/adminpack.sgml

@@ -22,7 +22,7 @@
   functions in <xref linkend="functions-admin-genfile-table"/>, which
   provide read-only access.)
   Only files within the database cluster directory can be accessed, unless the
-  user is a superuser or given privileges of one of the pg_read_server_files, 
+  user is a superuser or given privileges of one of the pg_read_server_files,
   or pg_write_server_files roles, as appropriate for the function, but either a
   relative or absolute path is allowable.
  </para>

doc/src/sgml/custom-rmgr.sgml

@@ -55,7 +55,7 @@ typedef struct RmgrData
     void        (*rm_decode) (struct LogicalDecodingContext *ctx,
                               struct XLogRecordBuffer *buf);
 } RmgrData;
-</programlisting>  
+</programlisting>
  </para>
  <para>
   Then, register your new resource
@@ -88,7 +88,7 @@ extern void RegisterCustomRmgr(RmgrId rmid, RmgrData *rmgr);
   during <productname>PostgreSQL</productname> startup.
  </para>
  <note>
-   <para>    
+   <para>
     The extension must remain in shared_preload_libraries as long as any
     custom WAL records may exist in the system. Otherwise
     <productname>PostgreSQL</productname> will not be able to apply or decode

doc/src/sgml/func.sgml

@@ -17758,7 +17758,7 @@ $.* ? (@ like_regex "^\\d+$")
      <title>Notes</title>
      <para>
       Alternatively, you can construct <acronym>JSON</acronym> values simply
-      using <productname>PostgreSQL</productname>-specific casts to 
+      using <productname>PostgreSQL</productname>-specific casts to
       <type>json</type> and <type>jsonb</type> types.
      </para>
     </sect5>
@@ -19127,7 +19127,7 @@ FROM my_films;
 SELECT
     JSON_QUERY(js, '$.favorites[*].kind' ERROR ON ERROR)
 FROM my_films;
-ERROR: more than one SQL/JSON item 
+ERROR: more than one SQL/JSON item
 </screen>
 
      <para>
@@ -19175,7 +19175,7 @@ SELECT JSON_QUERY(jsonb '"aaa"', '$' RETURNING text OMIT QUOTES);
 
 <synopsis>
 <replaceable class="parameter">expression</replaceable>
-  IS <optional> NOT </optional> JSON 
+  IS <optional> NOT </optional> JSON
   <optional> { VALUE | SCALAR | ARRAY | OBJECT } </optional>
   <optional> { WITH | WITHOUT } UNIQUE <optional> KEYS </optional> </optional>
 </synopsis>
@@ -19294,16 +19294,16 @@ SELECT JSON_QUERY(jsonb '"aaa"', '$' RETURNING text OMIT QUOTES);
      </para>
      <screen>
 SELECT
-    js, 
-    js IS JSON "is json", 
+    js,
+    js IS JSON "is json",
     js IS NOT JSON "is not json",
     js IS JSON SCALAR "is scalar",
     js IS JSON OBJECT "is object",
     js IS JSON ARRAY "is array"
-FROM 
+FROM
     (VALUES ('123'), ('"abc"'), ('{"a": "b"}'), ('[1,2]'), ('abc')) foo(js);
 
-     js     | is json | is not json | is scalar | is object | is array 
+     js     | is json | is not json | is scalar | is object | is array
 ------------+---------+-------------+-----------+-----------|-------------
  123        | t       | f           | t         | f         | f
  "abc"      | t       | f           | t         | f         | f
@@ -19704,7 +19704,7 @@ where <replaceable class="parameter">json_table_column</replaceable> is:
     <listitem>
 
     <para>
-     Use <literal>CROSS JOIN</literal>, so that the output includes 
+     Use <literal>CROSS JOIN</literal>, so that the output includes
      a row for every possible combination of rows from the left-hand
      and the right-hand columns.
     </para>
@@ -19743,7 +19743,7 @@ where <replaceable class="parameter">json_table_column</replaceable> is:
       some JSON data about the films and create a view that
       distributes the film genre, title, and director between separate columns:
 <screen>
-SELECT jt.* FROM 
+SELECT jt.* FROM
  my_films,
  JSON_TABLE ( js, '$.favorites[*]' COLUMNS (
    id FOR ORDINALITY,
@@ -19864,7 +19864,7 @@ JSON_SERIALIZE (
      <title>Notes</title>
      <para>
       Alternatively, you can construct <acronym>JSON</acronym> values simply
-      using <productname>PostgreSQL</productname>-specific casts to 
+      using <productname>PostgreSQL</productname>-specific casts to
       <type>json</type> and <type>jsonb</type> types.
      </para>
     </sect5>

doc/src/sgml/high-availability.sgml

@@ -548,7 +548,7 @@ protocol to make nodes agree on a serializable transactional order.
    rollforward will take considerably longer, so that technique only
    offers a solution for disaster recovery, not high availability.
    A standby server can also be used for read-only queries, in which case
-   it is called a <firstterm>hot standby</firstterm> server. See 
+   it is called a <firstterm>hot standby</firstterm> server. See
    <xref linkend="hot-standby"/> for more information.
   </para>
 

doc/src/sgml/pgwalinspect.sgml

@@ -150,7 +150,7 @@ postgres=# select start_lsn, end_lsn, prev_lsn, xid, resource_manager, record_ty
     <listitem>
      <para>
       This function is same as <function>pg_get_wal_records_info()</function>
-      except that it gets information of all the valid WAL records from 
+      except that it gets information of all the valid WAL records from
       <replaceable>start_lsn</replaceable> till the end of WAL.
      </para>
     </listitem>

doc/src/sgml/ref/pgbench.sgml

@@ -69,7 +69,7 @@ tps = 896.967014 (without initial connection time)
   The first seven lines report some of the most important parameter
   settings.
   The sixth line reports the maximum number of tries for transactions with
-  serialization or deadlock errors (see <xref linkend="failures-and-retries"/> 
+  serialization or deadlock errors (see <xref linkend="failures-and-retries"/>
   for more information).
   The eighth line reports the number of transactions completed
   and intended (the latter being just the product of number of clients

doc/src/sgml/runtime.sgml

@@ -2194,7 +2194,7 @@ pg_dumpall -p 5432 | psql -d postgres -p 5433
    <acronym>TLS</acronym> protocol. <acronym>SSL</acronym> protocols are the
    precursors to <acronym>TLS</acronym> protocols, and the term
    <acronym>SSL</acronym> is still used for encrypted connections even though
-   <acronym>SSL</acronym> protocols are no longer supported. 
+   <acronym>SSL</acronym> protocols are no longer supported.
    <acronym>SSL</acronym> is used interchangeably with <acronym>TLS</acronym>
    in <productname>PostgreSQL</productname>.