Trim trailing whitespace

2017-06-12 09:51:18 -04:00 · 2017-06-12 09:51:18 -04:00 · bf6e4c3c82
commit bf6e4c3c82
parent ddd7b22b22
10 changed files with 22 additions and 22 deletions
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@ -4361,7 +4361,7 @@ SELECT (regexp_match('foobarbequebaz', 'bar.*que'))[1];
   <para>
    Some examples:
 <programlisting>
- SELECT regexp_matches('foo', 'not there');
+SELECT regexp_matches('foo', 'not there');
 regexp_matches
 ----------------
 (0 rows)
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@ -1175,7 +1175,7 @@ synchronous_standby_names = 'FIRST 2 (s1, s2, s3)'
    An example of <varname>synchronous_standby_names</> for
    a quorum-based multiple synchronous standbys is:
 <programlisting>
- synchronous_standby_names = 'ANY 2 (s1, s2, s3)'
+synchronous_standby_names = 'ANY 2 (s1, s2, s3)'
 </programlisting>
    In this example, if four standby servers <literal>s1</>, <literal>s2</>,
    <literal>s3</> and <literal>s4</> are running, transaction commits will
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@ -5941,12 +5941,12 @@ char *PQencryptPasswordConn(PGconn *conn, const char *passwd, const char *user,
    <listitem>
     <para>
      Prepares the md5-encrypted form of a <productname>PostgreSQL</> password.
- <synopsis>
+<synopsis>
 char *PQencryptPassword(const char *passwd, const char *user);
- </synopsis>
-      <function>PQencryptPassword</> is an older, deprecated version of 
+</synopsis>
+      <function>PQencryptPassword</> is an older, deprecated version of
      <function>PQencryptPasswodConn</>. The difference is that
-      <function>PQencryptPassword</> does not 
+      <function>PQencryptPassword</> does not
      require a connection object, and <literal>md5</> is always used as the
      encryption algorithm.
     </para>
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@ -802,7 +802,7 @@ postgres   27093  0.0  0.0  30096  2752 ?        Ss   11:34   0:00 postgres: ser
    <row>
     <entry><structfield>backend_type</structfield></entry>
     <entry><type>text</type></entry>
-     <entry>Type of current backend. Possible types are 
+     <entry>Type of current backend. Possible types are
      <literal>autovacuum launcher</>, <literal>autovacuum worker</>,
      <literal>background worker</>, <literal>background writer</>,
      <literal>client backend</>, <literal>checkpointer</>,
@ -1827,7 +1827,7 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i
    the standby to catch up with the sending server assuming the current
    rate of replay.  Such a system would show similar times while new WAL is
    being generated, but would differ when the sender becomes idle.  In
-    particular, when the standby has caught up completely, 
+    particular, when the standby has caught up completely,
    <structname>pg_stat_replication</structname> shows the time taken to
    write, flush and replay the most recent reported WAL location rather than
    zero as some users might expect.  This is consistent with the goal of
--- a/doc/src/sgml/parallel.sgml
+++ b/doc/src/sgml/parallel.sgml
@ -275,7 +275,7 @@ EXPLAIN SELECT * FROM pgbench_accounts WHERE filler LIKE '%x%';
      <para>
        In a <emphasis>parallel sequential scan</>, the table's blocks will
        be divided among the cooperating processes.  Blocks are handed out one
-        at a time, so that access to the table remains sequential. 
+        at a time, so that access to the table remains sequential.
      </para>
    </listitem>
    <listitem>
--- a/doc/src/sgml/pgstattuple.sgml
+++ b/doc/src/sgml/pgstattuple.sgml
@ -119,13 +119,13 @@ free_percent       | 1.95
    </table>

    <note>
-      <para>
-        The <literal>table_len</literal> will always be greater than the sum
-        of the <literal>tuple_len</literal>, <literal>dead_tuple_len</literal>
-        and <literal>free_space</literal>. The difference is accounted for by
-        fixed page overhead, the per-page table of pointers to tuples, and
-        padding to ensure that tuples are correctly aligned. 
-      </para>
+     <para>
+      The <literal>table_len</literal> will always be greater than the sum
+      of the <literal>tuple_len</literal>, <literal>dead_tuple_len</literal>
+      and <literal>free_space</literal>. The difference is accounted for by
+      fixed page overhead, the per-page table of pointers to tuples, and
+      padding to ensure that tuples are correctly aligned.
+     </para>
    </note>

    <para>
--- a/doc/src/sgml/postgres-fdw.sgml
+++ b/doc/src/sgml/postgres-fdw.sgml
@ -566,7 +566,7 @@
     </para>
    </listitem>
   </itemizedlist>
-   These are less likely to be problematic than <varname>search_path</>, but 
+   These are less likely to be problematic than <varname>search_path</>, but
   can be handled with function <literal>SET</> options if the need arises.
  </para>

--- a/doc/src/sgml/protocol.sgml
+++ b/doc/src/sgml/protocol.sgml
@ -1352,7 +1352,7 @@ general, while the next subsection gives more details on SCRAM-SHA-256.
 <title>SASL Authentication Message Flow</title>

 <step id="sasl-auth-begin">
-<para>  
+<para>
  To begin a SASL authentication exchange, the server sends an
  AuthenticationSASL message. It includes a list of SASL authentication
  mechanisms that the server can accept, in the server's preferred order.
@ -1401,7 +1401,7 @@ ErrorMessage.
  <para>
    <firstterm>SCRAM-SHA-256</> (called just <firstterm>SCRAM</> from now on) is
    the only implemented SASL mechanism, at the moment. It is described in detail
-    in RFC 7677 and RFC 5802. 
+    in RFC 7677 and RFC 5802.
  </para>

  <para>
--- a/doc/src/sgml/ref/alter_table.sgml
+++ b/doc/src/sgml/ref/alter_table.sgml
@ -185,7 +185,7 @@ ALTER TABLE [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable>
      table.  Even if there is no <literal>NOT NULL</> constraint on the
      parent, such a constraint can still be added to individual partitions,
      if desired; that is, the children can disallow nulls even if the parent
-      allows them, but not the other way around. 
+      allows them, but not the other way around.
     </para>
    </listitem>
   </varlistentry>
@ -617,7 +617,7 @@ ALTER TABLE [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable>
     </para>

     <para>
-      <literal>SHARE UPDATE EXCLUSIVE</literal> lock will be taken for 
+      <literal>SHARE UPDATE EXCLUSIVE</literal> lock will be taken for
      fillfactor and autovacuum storage parameters, as well as the
      following planner related parameters:
      effective_io_concurrency, parallel_workers, seq_page_cost
--- a/doc/src/sgml/ref/copy.sgml
+++ b/doc/src/sgml/ref/copy.sgml
@ -425,7 +425,7 @@ COPY <replaceable class="parameter">count</replaceable>
   </para>

   <para>
-    If row-level security is enabled for the table, the relevant 
+    If row-level security is enabled for the table, the relevant
    <command>SELECT</command> policies will apply to <literal>COPY
    <replaceable class="parameter">table</> TO</literal> statements.
    Currently, <command>COPY FROM</command> is not supported for tables