Commita66e683

Michael Paquier

committed

Improve comment explaining how search_next_wal works with LSN

This makes the explanation a bit clearer, as the LSN in this functionis used with the current timeline to generate the file name.

1 parentced83f7 commita66e683Copy full SHA for a66e683

File tree

-1

lines changed

-1

lines changed

Lines changed: 6 additions & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -1021,7 +1021,12 @@ search_next_wal(const char path, XLogRecPtr need_lsn, parray *timelines)`
`1021`	`1021`	`parray_remove(timelines,i+1);`
`1022`	`1022`	`/* XXX: should we add a linebreak when we find a timeline? */`
`1023`	`1023`
`1024`		`-/* Move to next xlog segment */`
	`1024`	`+/*`
	`1025`	`+ * Move to next xlog segment. Note that we need to increment`
	`1026`	`+ * by XLogSegSize to jump directly to the next WAL segment file`
	`1027`	`+ * and as this value is used to generate the WAL file name with`
	`1028`	`+ * the current timeline of backup.`
	`1029`	`+ */`
`1025`	`1030`	`*need_lsn+=XLogSegSize;`
`1026`	`1031`	`}`
`1027`	`1032`	`}`

Comments

(0)