Commit 82c1507e authored by Alvaro Herrera's avatar Alvaro Herrera

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
parent 6af9f1bd
...@@ -4131,7 +4131,7 @@ CleanupBackupHistory(void) ...@@ -4131,7 +4131,7 @@ CleanupBackupHistory(void)
/* /*
* Attempt to read an XLOG record. * 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. * 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. * If no valid record is available, returns NULL, or fails if emode is PANIC.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment