Skip to content

Commit 2563f07

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 511d803 commit 2563f07

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
@@ -3244,7 +3244,7 @@ RestoreBackupBlockContents(XLogRecPtr lsn, BkpBlock bkpb, char *blk,
32443244
/*
32453245
* Attempt to read an XLOG record.
32463246
*
3247-
* If RecPtr is not NULL, try to read a record at that position. Otherwise
3247+
* If RecPtr is valid, try to read a record at that position. Otherwise
32483248
* try to read a record just after the last one previously read.
32493249
*
32503250
* If no valid record is available, returns NULL, or fails if emode is PANIC.

0 commit comments

Comments
 (0)