Commit1ca4a1b

committed

Finish up XLOG_HINT renaming

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

1 parent71d05a2 commit1ca4a1bCopy full SHA for 1ca4a1b

File tree

-2

lines changed

-2

lines changed

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -627,7 +627,7 @@ of optimising for performance. When a hint is written we use`
`627`	`627`	`MarkBufferDirtyHint() to mark the block dirty.`
`628`	`628`
`629`	`629`	`If the buffer is clean and checksums are in use then`
`630`		`-MarkBufferDirtyHint() inserts anXLOG_HINT record to ensure that we`
	`630`	`+MarkBufferDirtyHint() inserts anXLOG_FPI record to ensure that we`
`631`	`631`	`take a full page image that includes the hint. We do this to avoid`
`632`	`632`	`a partial page write, when we write the dirtied page. WAL is not`
`633`	`633`	`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
`@@ -3352,7 +3352,7 @@ IncrBufferRefCount(Buffer buffer)`
`3352`	`3352`	`* This is essentially the same as MarkBufferDirty, except:`
`3353`	`3353`	`*`
`3354`	`3354`	`* 1. The caller does not write WAL; so if checksums are enabled, we may need`
`3355`		`- * to write anXLOG_HINT WAL record to protect against torn pages.`
	`3355`	`+ * to write anXLOG_FPI WAL record to protect against torn pages.`
`3356`	`3356`	`* 2. The caller might have only share-lock instead of exclusive-lock on the`
`3357`	`3357`	`* buffer's content lock.`
`3358`	`3358`	`* 3. This function does not guarantee that the buffer is always marked dirty`

Comments

(0)