Finish up XLOG_HINT renaming

alvherre · alvherre · commit 1ca4a1b5d2c6 · 2016-06-17T18:05:55.000-04:00
Commit b8fd1a0 renamed XLOG_HINT to XLOG_FPI, but neglected two places. Backpatch to 9.3, like that commit.
diff --git a/src/backend/access/transam/README b/src/backend/access/transam/README
@@ -627,7 +627,7 @@ of optimising for performance. When a hint is written we use
 MarkBufferDirtyHint() to mark the block dirty.
 
 If the buffer is clean and checksums are in use then
-MarkBufferDirtyHint() inserts an XLOG_HINT record to ensure that we
+MarkBufferDirtyHint() inserts an XLOG_FPI record to ensure that we
 take a full page image that includes the hint. We do this to avoid
 a partial page write, when we write the dirtied page. WAL is not
 written during recovery, so we simply skip dirtying blocks because
diff --git a/src/backend/storage/buffer/bufmgr.c b/src/backend/storage/buffer/bufmgr.c
@@ -3352,7 +3352,7 @@ IncrBufferRefCount(Buffer buffer)
  * This is essentially the same as MarkBufferDirty, except:
  *
  * 1. The caller does not write WAL; so if checksums are enabled, we may need
- *	  to write an XLOG_HINT WAL record to protect against torn pages.
+ *	  to write an XLOG_FPI WAL record to protect against torn pages.
  * 2. The caller might have only share-lock instead of exclusive-lock on the
  *	  buffer's content lock.
  * 3. This function does not guarantee that the buffer is always marked dirty

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 an XLOG_HINT WAL record to protect against torn pages.`
	`3355`	`+ * to write an XLOG_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`