diff options
| -rw-r--r-- | src/backend/access/transam/README | 2 | ||||
| -rw-r--r-- | src/backend/storage/buffer/bufmgr.c | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/src/backend/access/transam/README b/src/backend/access/transam/README index 82ffb98680f..da3e677a34f 100644 --- 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 3600fd67c24..16d4f2839aa 100644 --- 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 |