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 69cadbcede9baff2ff99859eee19cffdf885c98d..9e2d09122bb7c80113d56beacca35b975c04c142 100644 (file)
--- a/src/backend/access/heap/hio.c
+++ b/src/backend/access/heap/hio.c
@@ -363,7 +363,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.c b/src/backend/utils/misc/guc.c
index d52aa9ae0e8de4827ddc4cf50bceb81f29fc15fb..ba1ca6f2552437a560d25b2dd419183c852a3fa4 100644 (file)
--- a/src/backend/utils/misc/guc.c
+++ b/src/backend/utils/misc/guc.c
@@ -1184,7 +1184,7 @@ static 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 3377fa56768001ebdf09d961f23f62b07e53fdbb..4bd63f8ca06f5ff0ed2dee4a29ce4af39aa0fe6c 100644 (file)
--- a/src/include/storage/buf_internals.h
+++ b/src/include/storage/buf_internals.h
@@ -149,7 +149,7 @@ typedef struct buftag
  * 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