Finish up XLOG_HINT renaming

Commit b8fd1a09f3 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
index bc68b470e09f817e6ddd4d7c44c7ca08db55d0f0..81b27a119a0ef86c12bce4250fe02b23ca069038 100644 (file)
--- a/src/backend/access/transam/README
+++ b/src/backend/access/transam/README
@@ -624,7 +624,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
index 75e3aa5ecdd3baffc67fe0d7be99e7c7692a1ce7..cf5b1e76caf086a41eb731b92e3d1fb4890925a9 100644 (file)
--- a/src/backend/storage/buffer/bufmgr.c
+++ b/src/backend/storage/buffer/bufmgr.c
@@ -3015,7 +3015,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