Skip to content

Commit 52a5eac

Browse files
committed
Fix typo in comment
Once upon a time, WAL pointers could be NULL, but no longer. We talk about "valid" now. Reported-by: Amit Langote Discussion: https://postgr.es/m/33e9617d-27f1-eee8-3311-e27af98eaf2b@lab.ntt.co.jp
1 parent 823a51e commit 52a5eac

File tree

1 file changed

+1
-1
lines changed
  • src/backend/access/transam

1 file changed

+1
-1
lines changed

src/backend/access/transam/xlog.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4132,7 +4132,7 @@ RestoreBackupBlockContents(XLogRecPtr lsn, BkpBlock bkpb, char *blk,
41324132
/*
41334133
* Attempt to read an XLOG record.
41344134
*
4135-
* If RecPtr is not NULL, try to read a record at that position. Otherwise
4135+
* If RecPtr is valid, try to read a record at that position. Otherwise
41364136
* try to read a record just after the last one previously read.
41374137
*
41384138
* If no valid record is available, returns NULL, or fails if emode is PANIC.

0 commit comments

Comments
 (0)