postgres.git / summary / log / commit / refs

commit    2563f079ec0217f672680d13d9d442a1ea6efc6a
Author:   Alvaro Herrera <alvherre@alvh.no-ip.org>
Date:     Thu Jun 22 20:42:38 2017 +0000

    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


 src/backend/access/transam/xlog.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/backend/access/transam/xlog.c b/src/backend/access/transam/xlog.c
index 0b6bd55eaff..4a5b20266ce 100644
--- a/src/backend/access/transam/xlog.c
+++ b/src/backend/access/transam/xlog.c
@@ -3244,7 +3244,7 @@ RestoreBackupBlockContents(XLogRecPtr lsn, BkpBlock bkpb, char *blk,
 /*
  * Attempt to read an XLOG record.
  *
- * If RecPtr is not NULL, try to read a record at that position.  Otherwise
+ * If RecPtr is valid, try to read a record at that position.  Otherwise
  * try to read a record just after the last one previously read.
  *
  * If no valid record is available, returns NULL, or fails if emode is PANIC.


[parent: 511d803ca41a]