On Wed, Sep 10, 2008 at 12:05 PM, Hannu Krosing <hannu@krosing.net> wrote:
>
>
>> Because, at the time, current WAL position might be in the middle of
>> WAL file. Even if the master sends only current WAL data, the slave
>> which don't have the corresponding WAL file can not handle it.
>
> I agree, that making initial copy may be outside the scope of
> Synchronous Log Shipping Replication, but slave catching up by
> requesting all missing WAL files and applying these up to a point when
> it can switch to Sync mode should be in. Else we gain very little from
> this patch.
>
I agree. We should leave the initial backup acquisition out of the
scope atleast for the first phase, but provide mechanism to do initial
catch up, as it may get messy to do it completely outside of the core.
The slave will need to able to buffer the *current* WAL until it gets
the missing WAL files and then continue. Also we may not want the
master to be stuck while slave is doing the catchup.
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
