Commitd300b8c

committed

Finish up XLOG_HINT renaming

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

1 parent519445b commitd300b8cCopy full SHA for d300b8c

File tree

-2

lines changed

-2

lines changed

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -596,7 +596,7 @@ of optimising for performance. When a hint is written we use`
`596`	`596`	`MarkBufferDirtyHint() to mark the block dirty.`
`597`	`597`
`598`	`598`	`If the buffer is clean and checksums are in use then`
`599`		`-MarkBufferDirtyHint() inserts anXLOG_HINT record to ensure that we`
	`599`	`+MarkBufferDirtyHint() inserts anXLOG_FPI record to ensure that we`
`600`	`600`	`take a full page image that includes the hint. We do this to avoid`
`601`	`601`	`a partial page write, when we write the dirtied page. WAL is not`
`602`	`602`	`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
`@@ -2640,7 +2640,7 @@ IncrBufferRefCount(Buffer buffer)`
`2640`	`2640`	`* This is essentially the same as MarkBufferDirty, except:`
`2641`	`2641`	`*`
`2642`	`2642`	`* 1. The caller does not write WAL; so if checksums are enabled, we may need`
`2643`		`- * to write anXLOG_HINT WAL record to protect against torn pages.`
	`2643`	`+ * to write anXLOG_FPI WAL record to protect against torn pages.`
`2644`	`2644`	`* 2. The caller might have only share-lock instead of exclusive-lock on the`
`2645`	`2645`	`* buffer's content lock.`
`2646`	`2646`	`* 3. This function does not guarantee that the buffer is always marked dirty`

Comments

(0)