Fix bug in streaming replication over multiple tli switches.

hlinnaka · hlinnaka · commit d194d7a52630 · 2013-01-02T14:35:15.000+02:00
After receiving some WAL over streaming replication, try to open the file
from the timeline we're currently recieving, not recoveryTargetTLI. They
are usually the same, which is why wasn't noticed before, but you'd get
an error if there have been more than one timeline switch between the
current point in WAL and the recovery target.
diff --git a/src/backend/access/transam/xlog.c b/src/backend/access/transam/xlog.c
@@ -9745,7 +9745,7 @@ WaitForWALToBecomeAvailable(XLogRecPtr RecPtr, bool randAccess,
 					if (readFile < 0)
 					{
 						readFile = XLogFileRead(readSegNo, PANIC,
-												recoveryTargetTLI,
+												receiveTLI,
 												XLOG_FROM_STREAM, false);
 						Assert(readFile >= 0);
 					}

Original file line number	Diff line number	Diff line change
`@@ -9745,7 +9745,7 @@ WaitForWALToBecomeAvailable(XLogRecPtr RecPtr, bool randAccess,`
`9745`	`9745`	`if (readFile < 0)`
`9746`	`9746`	`{`
`9747`	`9747`	`readFile = XLogFileRead(readSegNo, PANIC,`
`9748`		`- recoveryTargetTLI,`
	`9748`	`+ receiveTLI,`
`9749`	`9749`	`XLOG_FROM_STREAM, false);`
`9750`	`9750`	`Assert(readFile >= 0);`
`9751`	`9751`	`}`