diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2016-06-17 18:05:55 -0400 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2016-06-17 18:05:55 -0400 |
| commit | 1449b6ced5ba375fed814fda537718c2cd95a9b4 (patch) | |
| tree | b676d0c9efa2bca49d410d153f0ec95092a3ab62 /src | |
| parent | 2a8b5d2105fdb7d34b4a5911e6a4f5a39defac3f (diff) | |
| download | postgresql-1449b6ced5ba375fed814fda537718c2cd95a9b4.tar.gz postgresql-1449b6ced5ba375fed814fda537718c2cd95a9b4.zip | |
Finish up XLOG_HINT renaming
Commit b8fd1a09f3 renamed XLOG_HINT to XLOG_FPI, but neglected two
places.
Backpatch to 9.3, like that commit.
Diffstat (limited to 'src')
| -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 d86a911afe0..c91eabed882 100644 --- a/src/backend/access/transam/README +++ b/src/backend/access/transam/README @@ -601,7 +601,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 3ae203fde01..1c431240491 100644 --- a/src/backend/storage/buffer/bufmgr.c +++ b/src/backend/storage/buffer/bufmgr.c @@ -2639,7 +2639,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 |