Trim trailing whitespace

diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 14aae736c3427bc9581f3d64f4599e6462030729..7452d7cfa62c034cab8746ba07204a577dc09a77 100644 (file)
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -4361,7 +4361,7 @@ SELECT (regexp_match('foobarbequebaz', 'bar.*que'))[1];
    
     Some examples:
 
- SELECT regexp_matches('foo', 'not there');
+SELECT regexp_matches('foo', 'not there');
  regexp_matches
 ----------------
 (0 rows)

diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index 92e3b454fbfcfe9852110db8613d98629cc73bf5..ce67d4a5e3b22b4b6696de16ebd5568ebf5ab6da 100644 (file)
--- 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 synchronous_standby_names for
     a quorum-based multiple synchronous standbys is:
 
- synchronous_standby_names = 'ANY 2 (s1, s2, s3)'
+synchronous_standby_names = 'ANY 2 (s1, s2, s3)'
 
     In this example, if four standby servers s1, s2,
     s3 and s4 are running, transaction commits will

diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index 23e6f1c3dcd6ad35abf454d6e21e4a99a90f31f0..c3bd4f9b9bd3abf4ccf431a04f365a1d5061c152 100644 (file)
--- 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,
     
      
       Prepares the md5-encrypted form of a PostgreSQL password.
- 
+
 char *PQencryptPassword(const char *passwd, const char *user);
- 
-      PQencryptPassword is an older, deprecated version of 
+
+      PQencryptPassword is an older, deprecated version of
       PQencryptPasswodConn. The difference is that
-      PQencryptPassword does not 
+      PQencryptPassword does not
       require a connection object, and md5 is always used as the
       encryption algorithm.
      

diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 79ca45a15633477898c290098649939227c9a959..9ff5eea0388ddb99fd1a3c912e8d6ebfe6de6ec7 100644 (file)
--- 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
     
      backend_type
      text
-     Type of current backend. Possible types are 
+     Type of current backend. Possible types are
       autovacuum launcher, autovacuum worker,
       background worker, background writer,
       client backend, 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,
     pg_stat_replication 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

diff --git a/doc/src/sgml/parallel.sgml b/doc/src/sgml/parallel.sgml
index a65129078ccf808860125f1fde923866bda0d07d..ff31e7537e6cc3b6a1c27d23fe49b03bca67c0c9 100644 (file)
--- 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%';
       
         In a 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.
       
     
     

diff --git a/doc/src/sgml/pgstattuple.sgml b/doc/src/sgml/pgstattuple.sgml
index b6a5f19e706ba8d692a0f070add2292172b57c95..e98e04fa2fd2edb848caf727b7f39aea3c24cf31 100644 (file)
--- a/doc/src/sgml/pgstattuple.sgml
+++ b/doc/src/sgml/pgstattuple.sgml
@@ -119,13 +119,13 @@ free_percent       | 1.95
     
 
     
-      
-        The table_len will always be greater than the sum
-        of the tuple_len, dead_tuple_len
-        and free_space. 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. 
-      
+     
+      The table_len will always be greater than the sum
+      of the tuple_len, dead_tuple_len
+      and free_space. 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.
+     
     
 
     

diff --git a/doc/src/sgml/postgres-fdw.sgml b/doc/src/sgml/postgres-fdw.sgml
index 3dfc0f84ed3d3b6df72bbf0336663aa10b796bae..23558e7ec08e60d25301f3178bce8991f3793806 100644 (file)
--- a/doc/src/sgml/postgres-fdw.sgml
+++ b/doc/src/sgml/postgres-fdw.sgml
@@ -566,7 +566,7 @@
      
     
    
-   These are less likely to be problematic than search_path, but 
+   These are less likely to be problematic than search_path, but
    can be handled with function SET options if the need arises.
   
 

diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml
index 4837be5016c022c8cd378e07927c19fa2ff08e48..a7a3d3b2f9767d47796f36063689862c232729d2 100644 (file)
--- 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.
 SASL Authentication Message Flow
 
 
-  
+
   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.
   
     SCRAM-SHA-256 (called just 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.
   
 
   

diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml
index 4c61c442650b7a4bf593547a9b32aec53e3ebdbd..69600321e60a61e9305884b48d9b811ec9be9930 100644 (file)
--- a/doc/src/sgml/ref/alter_table.sgml
+++ b/doc/src/sgml/ref/alter_table.sgml
@@ -185,7 +185,7 @@ ALTER TABLE [ IF EXISTS ] name
       table.  Even if there is no 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.
      
     
    
@@ -617,7 +617,7 @@ ALTER TABLE [ IF EXISTS ] name
      
 
      
-      SHARE UPDATE EXCLUSIVE lock will be taken for 
+      SHARE UPDATE EXCLUSIVE 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

diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml
index 215efcd69d77f60ddd85afbe52bbf5b76972a391..8de1150dfb29208c8a7f4717b3d3bd85672349b3 100644 (file)
--- a/doc/src/sgml/ref/copy.sgml
+++ b/doc/src/sgml/ref/copy.sgml
@@ -425,7 +425,7 @@ COPY count
    
 
    
-    If row-level security is enabled for the table, the relevant 
+    If row-level security is enabled for the table, the relevant
     SELECT policies will apply to COPY
     table TO statements.
     Currently, COPY FROM is not supported for tables