Commitcd75e30

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 parent4f4a001 commitcd75e30Copy full SHA for cd75e30

File tree

-3

lines changed

-3

lines changed

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -363,7 +363,7 @@ RelationGetBufferForTuple(Relation relation, Size len,`
`363`	`363`	`* on, as cached in the BulkInsertState or relcache entry. If that`
`364`	`364`	`* doesn't work, we ask the Free Space Map to locate a suitable page.`
`365`	`365`	`* Since the FSM's info might be out of date, we have to be prepared to`
`366`		`- * loop around and retry multiple times. (Toinsure this isn't an infinite`
	`366`	`+ * loop around and retry multiple times. (Toensure this isn't an infinite`
`367`	`367`	`* loop, we must update the FSM with the correct amount of free space on`
`368`	`368`	`* each page that proves not to be suitable.) If the FSM has no record of`
`369`	`369`	`* 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
`@@ -1184,7 +1184,7 @@ static struct config_bool ConfigureNamesBool[] =`
`1184`	`1184`	`{"fsync",PGC_SIGHUP,WAL_SETTINGS,`
`1185`	`1185`	`gettext_noop("Forces synchronization of updates to disk."),`
`1186`	`1186`	`gettext_noop("The server will use the fsync() system call in several places to make "`
`1187`		`-"sure that updates are physically written to disk. Thisinsures "`
	`1187`	`+"sure that updates are physically written to disk. Thisensures "`
`1188`	`1188`	`"that a database cluster will recover to a consistent state after "`
`1189`	`1189`	`"an operating system or hardware crash.")`
`1190`	`1190`	`},`

Lines changed: 1 addition & 1 deletion

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

Comments

(0)