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 82ffb98680fdb3a678431d2fbb5577696e6f61a9..da3e677a34fa21b536a426758c23bb2dc660b94e 100644 (file)
--- a/src/backend/access/transam/README
+++ b/src/backend/access/transam/README
@@ -596,7 +596,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 3600fd67c241709c3507b61386432e0b66b275b4..16d4f2839aa7a0e2146e1bde5c750c10e69ca676 100644 (file)
--- a/src/backend/storage/buffer/bufmgr.c
+++ b/src/backend/storage/buffer/bufmgr.c
@@ -2640,7 +2640,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