Ensure we use the correct spelling of "ensure"

We seem to have accidentally used "insure" in a few places.  Correct
that.

Author: Peter Smith
Discussion: https://postgr.es/m/CAHut+Pv0biqrhA3pMhu40aDsj343mTsD75khKnHsLqR8P04f=Q@mail.gmail.com
Backpatch-through: 12, oldest supported version

diff --git a/src/backend/access/heap/hio.c b/src/backend/access/heap/hio.c
index caa62708aa5f243b70dab8737ef26acce46a9c05..ccc4c6966a2062f1c25d3db34bb2806139a27b73 100644 (file)
--- a/src/backend/access/heap/hio.c
+++ b/src/backend/access/heap/hio.c
@@ -563,7 +563,7 @@ RelationGetBufferForTuple(Relation relation, Size len,
     * on, as cached in the BulkInsertState or relcache entry.  If that
     * doesn't work, we ask the Free Space Map to locate a suitable page.
     * Since the FSM's info might be out of date, we have to be prepared to
-    * loop around and retry multiple times. (To insure this isn't an infinite
+    * loop around and retry multiple times. (To ensure this isn't an infinite
     * loop, we must update the FSM with the correct amount of free space on
     * each page that proves not to be suitable.)  If the FSM has no record of
     * a page with enough free space, we give up and extend the relation.

diff --git a/src/backend/utils/misc/guc_tables.c b/src/backend/utils/misc/guc_tables.c
index 7605eff9b9d3deef62de89d913b6571f08cc1bc1..beed72abbd6a1356f0e3723d969344093616714f 100644 (file)
--- a/src/backend/utils/misc/guc_tables.c
+++ b/src/backend/utils/misc/guc_tables.c
@@ -1111,7 +1111,7 @@ struct config_bool ConfigureNamesBool[] =
        {"fsync", PGC_SIGHUP, WAL_SETTINGS,
            gettext_noop("Forces synchronization of updates to disk."),
            gettext_noop("The server will use the fsync() system call in several places to make "
-                        "sure that updates are physically written to disk. This insures "
+                        "sure that updates are physically written to disk. This ensures "
                         "that a database cluster will recover to a consistent state after "
                         "an operating system or hardware crash.")
        },

diff --git a/src/include/storage/buf_internals.h b/src/include/storage/buf_internals.h
index e15a86eff99da35d8e4082388225d682a6d5ac4b..2c4fd92e39b8abee44c310afccd48636bab89149 100644 (file)
--- a/src/include/storage/buf_internals.h
+++ b/src/include/storage/buf_internals.h
@@ -213,7 +213,7 @@ BufMappingPartitionLockByIndex(uint32 index)
  * is held.  Thus buffer header lock holder can do complex updates of the
  * state variable in single write, simultaneously with lock release (cleaning
  * BM_LOCKED flag).  On the other hand, updating of state without holding
- * buffer header lock is restricted to CAS, which insure that BM_LOCKED flag
+ * buffer header lock is restricted to CAS, which ensures that BM_LOCKED flag
  * is not set.  Atomic increment/decrement, OR/AND etc. are not allowed.
  *
  * An exception is that if we have the buffer pinned, its tag can't change

diff --git a/src/tools/pg_bsd_indent/indent.c b/src/tools/pg_bsd_indent/indent.c
index 2fd877108343274102b98c8fcc0c060d9e4575e9..923fc34b858ee7c48fcd649c157cecc79a261582 100644 (file)
--- a/src/tools/pg_bsd_indent/indent.c
+++ b/src/tools/pg_bsd_indent/indent.c
@@ -608,7 +608,7 @@ check_type:
 
        parse(hd_type); /* let parser worry about if, or whatever */
        }
-       ps.search_brace = btype_2;  /* this should insure that constructs
+       ps.search_brace = btype_2;  /* this should ensure that constructs
                     * such as main(){...} and int[]{...}
                     * have their braces put in the right
                     * place */