Commit6fce92a

committed

Finish up XLOG_HINT renaming

Commitb8fd1a0 renamed XLOG_HINT to XLOG_FPI, but neglected twoplaces.Backpatch to 9.3, like that commit.

1 parenta41b14f commit6fce92aCopy full SHA for 6fce92a

File tree

-2

lines changed

-2

lines changed

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -624,7 +624,7 @@ of optimising for performance. When a hint is written we use`
`624`	`624`	`MarkBufferDirtyHint() to mark the block dirty.`
`625`	`625`
`626`	`626`	`If the buffer is clean and checksums are in use then`
`627`		`-MarkBufferDirtyHint() inserts anXLOG_HINT record to ensure that we`
	`627`	`+MarkBufferDirtyHint() inserts anXLOG_FPI record to ensure that we`
`628`	`628`	`take a full page image that includes the hint. We do this to avoid`
`629`	`629`	`a partial page write, when we write the dirtied page. WAL is not`
`630`	`630`	`written during recovery, so we simply skip dirtying blocks because`

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -3015,7 +3015,7 @@ IncrBufferRefCount(Buffer buffer)`
`3015`	`3015`	`* This is essentially the same as MarkBufferDirty, except:`
`3016`	`3016`	`*`
`3017`	`3017`	`* 1. The caller does not write WAL; so if checksums are enabled, we may need`
`3018`		`- * to write anXLOG_HINT WAL record to protect against torn pages.`
	`3018`	`+ * to write anXLOG_FPI WAL record to protect against torn pages.`
`3019`	`3019`	`* 2. The caller might have only share-lock instead of exclusive-lock on the`
`3020`	`3020`	`* buffer's content lock.`
`3021`	`3021`	`* 3. This function does not guarantee that the buffer is always marked dirty`

Comments

(0)