On Friday, May 10, 2013 2:07 PM Kyotaro HORIGUCHI wrote: > Thank you for noticing me of that. > > > It seems to me, it is the same problem as discussed and fixed in > below > > thread. > > http://www.postgresql.org/message-id/51894942.4080...@vmware.com > > > > Could you try with fixes given by heikki. > > The first one settles the timeline transition problem for the > present. Besides, I have no longer found any recovery failure > except unrepeatable one shown below. > > > C 2013-05-10 15:30:29.589 JST 9242 LOG: restarted WAL streaming at > 0/5000000 on timeline 2 > > B 2013-05-10 15:30:33.789 JST 9233 LOG: restartpoint complete: > (snip.) > > B 2013-05-10 15:30:33.789 JST 9233 LOG: recovery restart point at > 0/3000028 > > B 2013-05-10 15:30:33.789 JST 9233 LOG: checkpoint starting: > > C 2013-05-10 15:32:32.170 JST 9242 FATAL: could not receive data > from WAL stream:
Is there any chance, that there is any network glitch caused this one time error. > I'm get confused, the patch seems to me ensureing the "first > checkpoint after fast promotion is performed" to use the > "correct, new, ThisTimeLineID". What is your confusion? With Regards, Amit Kapila. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
