On 13.10.2010 08:21, Fujii Masao wrote:
On Sat, Oct 9, 2010 at 4:31 AM, Heikki Linnakangas
<heikki.linnakan...@enterprisedb.com> wrote:
It shouldn't be too hard to fix. Walsender needs to be able to read WAL from
preceding timelines, like recovery does, and walreceiver needs to write the
incoming WAL to the right file.
And walsender seems to need to transfer the current timeline history to
the standby. Otherwise, the standby cannot recover the WAL file with new
timeline. And the standby might need to create the timeline history file
in order to recover the WAL file with new timeline even after it's restarted.
Yes, true, you need that too.
It might be good to divide this work into two phases, teaching archive
recovery to notice new timelines appearing in the archive first, and
doing the walsender/walreceiver changes after that.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
