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
This commit is contained in:
David Rowley 2023-11-10 00:17:07 +13:00
parent 308a69a987
commit 456d697bae
3 changed files with 3 additions and 3 deletions

View File

@ -387,7 +387,7 @@ RelationGetBufferForTuple(Relation relation, Size len,
* on, as cached in the BulkInsertState or relcache entry. If that * 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. * 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 * 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 * 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 * 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. * a page with enough free space, we give up and extend the relation.

View File

@ -1285,7 +1285,7 @@ static struct config_bool ConfigureNamesBool[] =
{"fsync", PGC_SIGHUP, WAL_SETTINGS, {"fsync", PGC_SIGHUP, WAL_SETTINGS,
gettext_noop("Forces synchronization of updates to disk."), gettext_noop("Forces synchronization of updates to disk."),
gettext_noop("The server will use the fsync() system call in several places to make " 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 " "that a database cluster will recover to a consistent state after "
"an operating system or hardware crash.") "an operating system or hardware crash.")
}, },

View File

@ -150,7 +150,7 @@ typedef struct buftag
* is held. Thus buffer header lock holder can do complex updates of the * is held. Thus buffer header lock holder can do complex updates of the
* state variable in single write, simultaneously with lock release (cleaning * state variable in single write, simultaneously with lock release (cleaning
* BM_LOCKED flag). On the other hand, updating of state without holding * 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. * 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 * An exception is that if we have the buffer pinned, its tag can't change