mirror of
https://github.com/postgrespro/pg_probackup.git
synced 2025-01-09 14:45:47 +02:00
Improve comment explaining how search_next_wal works with LSN
This makes the explanation a bit clearer, as the LSN in this function is used with the current timeline to generate the file name.
This commit is contained in:
parent
ced83f7703
commit
a66e683dd4
@ -1021,7 +1021,12 @@ search_next_wal(const char *path, XLogRecPtr *need_lsn, parray *timelines)
|
|||||||
parray_remove(timelines, i + 1);
|
parray_remove(timelines, i + 1);
|
||||||
/* XXX: should we add a linebreak when we find a timeline? */
|
/* XXX: should we add a linebreak when we find a timeline? */
|
||||||
|
|
||||||
/* Move to next xlog segment */
|
/*
|
||||||
|
* Move to next xlog segment. Note that we need to increment
|
||||||
|
* by XLogSegSize to jump directly to the next WAL segment file
|
||||||
|
* and as this value is used to generate the WAL file name with
|
||||||
|
* the current timeline of backup.
|
||||||
|
*/
|
||||||
*need_lsn += XLogSegSize;
|
*need_lsn += XLogSegSize;
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
Loading…
Reference in New Issue
Block a user