On Tue, Nov 22, 2016 at 8:48 AM, Tsunakawa, Takayuki <tsunakawa.ta...@jp.fujitsu.com> wrote: > From: pgsql-hackers-ow...@postgresql.org > > If the problem occurs, the following pair of lines appear in the server log > of the cascading standby. Could you check it? > > LOG: restored log file "000000020000000000000003" from archive > LOG: out-of-sequence timeline ID 1 (after 2) in log file 0, segment 3, > offset 0 >
Thanks for the clarification, I could reproduce the issue and confirms that patch has fixed it. Find logs of cascading standby at PG9.2 Head and Patch attached (I have truncated few lines at end of server log generated in Head as those were repetitive). I think the way you have directly explained the bug steps in code comments is not right (think if we start writing bug steps for each bug fix, how the code will look like). So I have modified the comment to explain the situation and reason of check, see if you find that as okay? -- With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com
postgresql_Thu_Patch.log
Description: Binary data
postgresql_Thu_Head.log
Description: Binary data
cascading_standby_stuck_v3.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers