Commit456d697

committed

Ensure we use the correct spelling of "ensure"

We seem to have accidentally used "insure" in a few places. Correctthat.Author: Peter SmithDiscussion:https://postgr.es/m/CAHut+Pv0biqrhA3pMhu40aDsj343mTsD75khKnHsLqR8P04f=Q@mail.gmail.comBackpatch-through: 12, oldest supported version

1 parent308a69a commit456d697Copy full SHA for 456d697

File tree

-3

lines changed

-3

lines changed

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -387,7 +387,7 @@ RelationGetBufferForTuple(Relation relation, Size len,`
`387`	`387`	`* on, as cached in the BulkInsertState or relcache entry. If that`
`388`	`388`	`* doesn't work, we ask the Free Space Map to locate a suitable page.`
`389`	`389`	`* Since the FSM's info might be out of date, we have to be prepared to`
`390`		`- * loop around and retry multiple times. (Toinsure this isn't an infinite`
	`390`	`+ * loop around and retry multiple times. (Toensure this isn't an infinite`
`391`	`391`	`* loop, we must update the FSM with the correct amount of free space on`
`392`	`392`	`* each page that proves not to be suitable.) If the FSM has no record of`
`393`	`393`	`* a page with enough free space, we give up and extend the relation.`

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -1285,7 +1285,7 @@ static struct config_bool ConfigureNamesBool[] =`
`1285`	`1285`	`{"fsync",PGC_SIGHUP,WAL_SETTINGS,`
`1286`	`1286`	`gettext_noop("Forces synchronization of updates to disk."),`
`1287`	`1287`	`gettext_noop("The server will use the fsync() system call in several places to make "`
`1288`		`-"sure that updates are physically written to disk. Thisinsures "`
	`1288`	`+"sure that updates are physically written to disk. Thisensures "`
`1289`	`1289`	`"that a database cluster will recover to a consistent state after "`
`1290`	`1290`	`"an operating system or hardware crash.")`
`1291`	`1291`	`},`

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -150,7 +150,7 @@ typedef struct buftag`
`150`	`150`	`* is held. Thus buffer header lock holder can do complex updates of the`
`151`	`151`	`* state variable in single write, simultaneously with lock release (cleaning`
`152`	`152`	`* BM_LOCKED flag). On the other hand, updating of state without holding`
`153`		`- * buffer header lock is restricted to CAS, whichinsure that BM_LOCKED flag`
	`153`	`+ * buffer header lock is restricted to CAS, whichensures that BM_LOCKED flag`
`154`	`154`	`* is not set. Atomic increment/decrement, OR/AND etc. are not allowed.`
`155`	`155`	`*`
`156`	`156`	`* An exception is that if we have the buffer pinned, its tag can't change`

Comments

(0)