On Mon, Aug 24, 2009 at 12:45 PM, james bardin<jbar...@bu.edu> wrote: >> >> I tried recovery_target_timeline='X' on the standby, where X is the >> new timeline created after recovery on the new master. This fails, >> with some "unexpected timeline ID" lines and a >> PANIC: could not locate a valid checkpoint record >> >> I also tried using recovery_target_timeline='latest'. This fell back >> gracefully to an earlier state, but changes were lost. Also, it never >> waited on pg_standby, and finished recovering immediately.
It seems that this is related the the issue in this bug report: http://archives.postgresql.org/pgsql-bugs/2009-05/msg00060.php The follow up is very long, and I couldn't formulate any workaround for the issue. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
