Hi, On Fri, May 15, 2009 at 8:20 PM, Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> wrote: > The probe in findNewestTimeLine() initialized to recovery target timeline + > 1. It doesn't require history files for any old timelines to be present.
What if recovery_target_timeline = 'latest'? The unexpected (not latest) recovery target timeline might be chosen when some timeline history files don't exist. > The > purpose of findNewestTimeLine() is to ensure that if you e.g recover to a > point in time in timeline 5, and there's already WAL files for timelines 6 > and 7 in the archive, we pick a unique timeline id. When only the history file for timeline 6 is deleted, timeline 6 would be assigned as the newest one *again* at the end of archive recovery. Is this safe? Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs