Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit078c9cd

Browse files
committed
Fix comment in xlogutils.c
The existing callers of XLogReadDetermineTimeline() performing recoveryneed to check a replay LSN position when determining on which timelineto read a WAL page. A portion of the comment describing this functionsaid exactly that, while referring to a routine for fetching a writeLSN, something not available in recovery.Author: Kyotaro HoriguchiDiscussion:https://postgr.es/m/20200511.101619.2043820539323292957.horikyota.ntt@gmail.com
1 parent81ec990 commit078c9cd

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

‎src/backend/access/transam/xlogutils.c

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -681,10 +681,10 @@ XLogTruncateRelation(RelFileNode rnode, ForkNumber forkNum,
681681
* copied to a new timeline.
682682
*
683683
* The caller must also make sure it doesn't read past the current replay
684-
* position (usingGetWalRcvWriteRecPtr) if executing in recovery, so it
684+
* position (usingGetXLogReplayRecPtr) if executing in recovery, so it
685685
* doesn't fail to notice that the current timeline became historical. The
686686
* caller must also update ThisTimeLineID with the result of
687-
*GetWalRcvWriteRecPtr and must check RecoveryInProgress().
687+
*GetXLogReplayRecPtr and must check RecoveryInProgress().
688688
*/
689689
void
690690
XLogReadDetermineTimeline(XLogReaderState*state,XLogRecPtrwantPage,uint32wantLength)

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp