Fix some cases of "the the" split across two lines.

Kevin Grittner observed that 2186b608b3cb859fe0ec04015a5c4e4cbf69caed
introduced a new occurence of this by copying existing text, and I
found a few more cases using grep.

Discussion: http://postgr.es/m/CADAecHWfG-K+YvocHCkrXV-ycm+eUOaaUVfYZNOnwf0pSmuQCw@mail.gmail.com

diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml
index 61ce12c56009e31a4a0a046c7b54f2b6a6b96bbe..ea655a10a8992a7b6817ee9f37362c0c35b0db91 100644 (file)
--- a/doc/src/sgml/catalogs.sgml
+++ b/doc/src/sgml/catalogs.sgml
@@ -3783,7 +3783,7 @@ SCRAM-SHA-256$<replaceable>&lt;iteration count&gt;</>:<replaceable>&lt;salt&gt;<
       <entry><literal><link linkend="catalog-pg-collation"><structname>pg_collation</structname></link>.oid</literal></entry>
       <entry>
        For each column in the index key, this contains the OID of the
-       the collation to use for the index, or zero if the column is not
+       collation to use for the index, or zero if the column is not
        of a collatable data type.
       </entry>
      </row>
@@ -4771,7 +4771,7 @@ SCRAM-SHA-256$<replaceable>&lt;iteration count&gt;</>:<replaceable>&lt;salt&gt;<
       <entry><literal><link linkend="catalog-pg-opclass"><structname>pg_opclass</structname></link>.oid</literal></entry>
       <entry>
        For each column in the partition key, this contains the OID of the
-       the collation to use for partitioning, or zero if the column is not
+       collation to use for partitioning, or zero if the column is not
        of a collatable data type.
       </entry>
      </row>

diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
index 84c4f209909072a755c993eaf2ba53e16f6eec6f..ec015e93d07740a24ecc28ab74d12b4b9c33fddd 100644 (file)
--- a/doc/src/sgml/ddl.sgml
+++ b/doc/src/sgml/ddl.sgml
@@ -3165,7 +3165,7 @@ CREATE INDEX ON measurement_y2008m01 (logdate);
 
     <para>
       Normally the set of partitions established when initially defining the
-      the table are not intended to remain static.  It is common to want to
+      table are not intended to remain static.  It is common to want to
       remove old partitions of data and periodically add new partitions for
       new data. One of the most important advantages of partitioning is
       precisely that it allows this otherwise painful task to be executed

diff --git a/src/bin/pg_basebackup/receivelog.c b/src/bin/pg_basebackup/receivelog.c
index cf730da283a578378d4e8c11e9df863843b7a29b..52aa274bb8972035c3cd6e7b2d8ded4c1e408ed8 100644 (file)
--- a/src/bin/pg_basebackup/receivelog.c
+++ b/src/bin/pg_basebackup/receivelog.c
@@ -629,7 +629,7 @@ ReceiveXlogStream(PGconn *conn, StreamCtl *stream)
                         * server had sent us half of a WAL record, when it was promoted.
                         * The new timeline will begin at the end of the last complete
                         * record in that case, overlapping the partial WAL record on the
-                        * the old timeline.
+                        * old timeline.
                         */
                        uint32          newtimeline;
                        bool            parsed;