From 8b5a3998a104ef5918b50e207be0aa86e085d49d Mon Sep 17 00:00:00 2001
From: Peter Eisentraut <peter_e@gmx.net>
Date: Thu, 30 May 2013 21:05:07 -0400
Subject: Remove whitespace from end of lines

---
 doc/src/sgml/maintenance.sgml      | 2 +-
 doc/src/sgml/ref/create_table.sgml | 2 +-
 doc/src/sgml/ref/notify.sgml       | 2 +-
 doc/src/sgml/ref/pg_dump.sgml      | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

(limited to 'doc/src')

diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
index d2bd68f501a..c05b5262cb3 100644
--- a/doc/src/sgml/maintenance.sgml
+++ b/doc/src/sgml/maintenance.sgml
@@ -632,7 +632,7 @@ HINT:  Stop the postmaster and use a standalone backend to VACUUM in "mydb".
     <varname>autovacuum_max_workers</> databases to be processed,
     the next database will be processed as soon as the first worker finishes.
     Each worker process will check each table within its database and
-    execute <command>VACUUM</> and/or <command>ANALYZE</> as needed. 
+    execute <command>VACUUM</> and/or <command>ANALYZE</> as needed.
     <varname>log_autovacuum_min_duration</varname> can be used to monitor
     autovacuum activity.
    </para>
diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml
index 2f0fa53a41a..26eca6731c2 100644
--- a/doc/src/sgml/ref/create_table.sgml
+++ b/doc/src/sgml/ref/create_table.sgml
@@ -336,7 +336,7 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI
      <para>
       Not-null constraints are always copied to the new table.
       <literal>CHECK</literal> constraints will be copied only if
-      <literal>INCLUDING CONSTRAINTS</literal> is specified. 
+      <literal>INCLUDING CONSTRAINTS</literal> is specified.
       Indexes, <literal>PRIMARY KEY</>, and <literal>UNIQUE</> constraints
       on the original table will be created on the new table only if the
       <literal>INCLUDING INDEXES</literal> clause is specified.
diff --git a/doc/src/sgml/ref/notify.sgml b/doc/src/sgml/ref/notify.sgml
index a9405fdd313..307d2f62825 100644
--- a/doc/src/sgml/ref/notify.sgml
+++ b/doc/src/sgml/ref/notify.sgml
@@ -33,7 +33,7 @@ NOTIFY <replaceable class="PARAMETER">channel</replaceable> [ , <replaceable cla
    with an optional <quote>payload</> string to each client application that
    has previously executed
    <command>LISTEN <replaceable class="parameter">channel</></command>
-   for the specified channel name in the current database. 
+   for the specified channel name in the current database.
    Notifications are visible to all users.
   </para>
 
diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml
index 40ca18c75f2..2b5e95bfe9a 100644
--- a/doc/src/sgml/ref/pg_dump.sgml
+++ b/doc/src/sgml/ref/pg_dump.sgml
@@ -324,7 +324,7 @@ PostgreSQL documentation
         For a consistent backup, the database server needs to support synchronized snapshots,
         a feature that was introduced in <productname>PostgreSQL</productname> 9.2. With this
         feature, database clients can ensure they see the same data set even though they use
-        different connections. <command>pg_dump -j</command> uses multiple database 
+        different connections. <command>pg_dump -j</command> uses multiple database
         connections; it connects to the database once with the master process and
         once again for each worker job. Without the synchronized snapshot feature, the
         different worker jobs wouldn't be guaranteed to see the same data in each connection,
-- 
cgit v1.2.3