--- Brad Nicholson <bnichols at ca.afilias.info> wrote:

>
> The statement above was about how you could easily
> move the big table 
> into its own set, if you wanted to.
> 
> Subscribing a set will not lock the tables on the
> master (or the 
> subscriber - but you will not see the data on the
> subscriber until the 
> subscription is complete).  You will place
> additional load on that db 
> while doing the subscribe, but at no point during a
> subscription will 
> writes or reads to/from the master database be
> blocked.
> 
> 

Thanks for clearing it up for me. In this case, it is
OK for the slave to take a while to catch up as long
as the master is usable. I just hope my app does not
have to fail over during the subscription :-)

Ujwal