Fix double-word typos

Discussion: https://postgr.es/m/20190612184527.GA24266@alvherre.pgsql
Reviewed-by: Michaël Paquier

diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index b67da8916a5d365b88c97ebeba0201dc1aaa218e..9d4c000df0b2ca2abf56387acbce05f232ecbd8c 100644 (file)
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -965,7 +965,7 @@ SELECT * FROM pg_stop_backup(false, true);
      backups.  Moreover, because it writes a backup_label file on the
      master, it can cause the master to fail to restart automatically after
      a crash.  On the other hand, the erroneous removal of a backup_label
-     file from a backup or standby is a common mistake which can can result
+     file from a backup or standby is a common mistake which can result
      in serious data corruption.  If it is necessary to use this method,
      the following steps may be used.
     </para>

diff --git a/src/bin/pg_dump/pg_dump.c b/src/bin/pg_dump/pg_dump.c
index 36e8d27edd862a1ba239b9e1a7bdf9a50acdaf31..8909a45d618d3170d59e7faae50d238bff0887ef 100644 (file)
--- a/src/bin/pg_dump/pg_dump.c
+++ b/src/bin/pg_dump/pg_dump.c
@@ -4051,8 +4051,8 @@ dumpPublicationTable(Archive *fout, PublicationRelInfo *pubrinfo)
                                          fmtQualifiedDumpable(tbinfo));
 
        /*
-        * There is no point in creating drop query as drop query as the drop is
-        * done by table drop.
+        * There is no point in creating drop query as the drop is done by table
+        * drop.
         */
        ArchiveEntry(fout, pubrinfo->dobj.catId, pubrinfo->dobj.dumpId,
                                 ARCHIVE_OPTS(.tag = tag,

diff --git a/src/include/executor/tuptable.h b/src/include/executor/tuptable.h
index d9122803863b354d5d2dfa4396962e7bb00437be..0710a7dd3880305fbbebe56296740cf9d58680ef 100644 (file)
--- a/src/include/executor/tuptable.h
+++ b/src/include/executor/tuptable.h
@@ -59,7 +59,7 @@
  * also that a virtual tuple does not have any "system columns".
  *
  * The Datum/isnull arrays of a TupleTableSlot serve double duty.  For virtual
- * slots they they are the authoritative data.  For the other builtin slots,
+ * slots they are the authoritative data.  For the other builtin slots,
  * the arrays contain data extracted from the tuple.  (In this state, any
  * pass-by-reference Datums point into the physical tuple.)  The extracted
  * information is built "lazily", ie, only as needed.  This serves to avoid

diff --git a/src/include/fmgr.h b/src/include/fmgr.h
index 1ac71a40f55a23718c4a3195b72266d1ea9681ad..3ff099986b838267f85000ac13398b5a98a4a5ba 100644 (file)
--- a/src/include/fmgr.h
+++ b/src/include/fmgr.h
@@ -96,7 +96,7 @@ typedef struct FunctionCallInfoBaseData
 } FunctionCallInfoBaseData;
 
 /*
- * Space needed for for a FunctionCallInfoBaseData struct with sufficient space
+ * Space needed for a FunctionCallInfoBaseData struct with sufficient space
  * for `nargs` arguments.
  */
 #define SizeForFunctionCallInfo(nargs) \

diff --git a/src/include/utils/snapshot.h b/src/include/utils/snapshot.h
index 9f92ce011db959cf4c73f3adc94160b9dc33a635..c00f1fe908524014b3ad0491ca0a4ac48722854b 100644 (file)
--- a/src/include/utils/snapshot.h
+++ b/src/include/utils/snapshot.h
@@ -69,7 +69,7 @@ typedef enum SnapshotType
        SNAPSHOT_ANY,
 
        /*
-        * A tuple is visible iff the tuple tuple is valid as a TOAST row.
+        * A tuple is visible iff the tuple is valid as a TOAST row.
         */
        SNAPSHOT_TOAST,
 

diff --git a/src/interfaces/ecpg/preproc/type.c b/src/interfaces/ecpg/preproc/type.c
index 165b5df24f3b203c4ef89ad5b78df833a94eb72b..6a71766ccf3ada5b0c6ad50a27c8e2ffa9ac7f93 100644 (file)
--- a/src/interfaces/ecpg/preproc/type.c
+++ b/src/interfaces/ecpg/preproc/type.c
@@ -582,7 +582,7 @@ ECPGdump_a_struct(FILE *o, const char *name, const char *ind_name, char *arrsize
 {
        /*
         * If offset is NULL, then this is the first recursive level. If not then
-        * we are in a struct in a struct and the offset is used as offset.
+        * we are in a struct and the offset is used as offset.
         */
        struct ECPGstruct_member *p,
                           *ind_p = NULL;

diff --git a/src/test/modules/test_integerset/test_integerset.c b/src/test/modules/test_integerset/test_integerset.c
index 15b9ce1ac3c01a3991015d97893eb568679ab573..e3925a156d61ba6c9a58e5124e0697e81d3eee2b 100644 (file)
--- a/src/test/modules/test_integerset/test_integerset.c
+++ b/src/test/modules/test_integerset/test_integerset.c
@@ -246,7 +246,7 @@ test_pattern(const test_spec *spec)
                 * last integer that we added to the set, plus an arbitrary constant
                 * (1000).  There's no point in probing the whole 0 - 2^64 range, if
                 * only a small part of the integer space is used.  We would very
-                * rarely hit hit values that are actually in the set.
+                * rarely hit values that are actually in the set.
                 */
                x = (pg_lrand48() << 31) | pg_lrand48();
                x = x % (last_int + 1000);
@@ -337,8 +337,8 @@ test_single_value(uint64 value)
                elog(ERROR, "intset_num_entries returned " UINT64_FORMAT ", expected 1", num_entries);
 
        /*
-        * Test intset_is_member() at various special values, like 0 and and
-        * maximum possible 64-bit integer, as well as the value itself.
+        * Test intset_is_member() at various special values, like 0 and maximum
+        * possible 64-bit integer, as well as the value itself.
         */
        if (intset_is_member(intset, 0) != (value == 0))
                elog(ERROR, "intset_is_member failed for 0");

diff --git a/src/test/recovery/t/013_crash_restart.pl b/src/test/recovery/t/013_crash_restart.pl
index 3ecb9dd4df787d53387bc0343893e9fcdb457278..2c477978e7dabe835f8c4fdd025f79335c76cc42 100644 (file)
--- a/src/test/recovery/t/013_crash_restart.pl
+++ b/src/test/recovery/t/013_crash_restart.pl
@@ -185,7 +185,7 @@ $monitor_stderr = '';
 
 
 # kill with SIGKILL this time - we expect the backend to exit, without
-# being able to emit an error error message
+# being able to emit an error message
 $ret = TestLib::system_log('pg_ctl', 'kill', 'KILL', $pid);
 is($ret, 0, "killed process with KILL");
 

diff --git a/src/test/regress/expected/polygon.out b/src/test/regress/expected/polygon.out
index f319239b2e4cfa1601d0ef12b09ed5bfead0459e..a1f5cce5cb20b3f1493100292dfc76898e14c26f 100644 (file)
--- a/src/test/regress/expected/polygon.out
+++ b/src/test/regress/expected/polygon.out
@@ -69,7 +69,7 @@ SET enable_bitmapscan = OFF;
 CREATE TEMP TABLE quad_poly_tbl_ord_seq2 AS
 SELECT rank() OVER (ORDER BY p <-> point '123,456') n, p <-> point '123,456' dist, id
 FROM quad_poly_tbl WHERE p <@ polygon '((300,300),(400,600),(600,500),(700,200))';
--- check results results from index scan
+-- check results from index scan
 SET enable_seqscan = OFF;
 SET enable_indexscan = OFF;
 SET enable_bitmapscan = ON;

diff --git a/src/test/regress/sql/polygon.sql b/src/test/regress/sql/polygon.sql
index 866e11b9e335e1afd827327cbe6cf06a0cefa6ac..03fc6a8576af5d625b8f1677b7d58742faa36dfc 100644 (file)
--- a/src/test/regress/sql/polygon.sql
+++ b/src/test/regress/sql/polygon.sql
@@ -66,7 +66,7 @@ CREATE TEMP TABLE quad_poly_tbl_ord_seq2 AS
 SELECT rank() OVER (ORDER BY p <-> point '123,456') n, p <-> point '123,456' dist, id
 FROM quad_poly_tbl WHERE p <@ polygon '((300,300),(400,600),(600,500),(700,200))';
 
--- check results results from index scan
+-- check results from index scan
 SET enable_seqscan = OFF;
 SET enable_indexscan = OFF;
 SET enable_bitmapscan = ON;