Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 4c004dd

Browse files
author
Amit Kapila
committed
Consistently use the function name CreateCheckPoint in code and comments.
Author: Bharath Rupireddy Discussion: https://postgr.es/m/CALj2ACVZmKsvDjtd45+9oTcnjUJtC4LF2BYK8TpWT1f=NjJX3w@mail.gmail.com
1 parent dc68668 commit 4c004dd

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

src/backend/storage/buffer/bufmgr.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3907,7 +3907,7 @@ MarkBufferDirtyHint(Buffer buffer, bool buffer_std)
39073907
* never gets written, so crash recovery will fix.
39083908
*
39093909
* It's possible we may enter here without an xid, so it is
3910-
* essential that CreateCheckpoint waits for virtual transactions
3910+
* essential that CreateCheckPoint waits for virtual transactions
39113911
* rather than full transactionids.
39123912
*/
39133913
MyProc->delayChkpt = delayChkpt = true;

src/backend/storage/ipc/standby.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1182,7 +1182,7 @@ standby_redo(XLogReaderState *record)
11821182
* starting to accumulate changes at a point just prior to when we derive
11831183
* the snapshot on the primary, then ignore duplicates when we later apply
11841184
* the snapshot from the running xacts record. This is implemented during
1185-
* CreateCheckpoint() where we use the logical checkpoint location as
1185+
* CreateCheckPoint() where we use the logical checkpoint location as
11861186
* our starting point and then write the running xacts record immediately
11871187
* before writing the main checkpoint WAL record. Since we always start
11881188
* up from a checkpoint and are immediately at our starting point, we

0 commit comments

Comments
 (0)