Melvin Davidson <melvin6925 at yahoo.com> writes:
>>Thanks! That worked, but I had to start up the Slon process as the script was
>>running. Previously when we did not have cascaded slaves, we ran the setup
>>scripts and then started Slon on all the servers.
>>Is there a right way to do it? Should you run the slon process on the
>>servers first and then run the slon setup script on the Master.
>
> I don't believe there is an "official" right way to do it.
> What always works for me though is two scripts.
> I run one to do the initialize of slony (nodes, paths, tables & seq adds)
> Then I start slon on ALL nodes.
> Then I run the second set to do subscribes.

Things are sufficiently asynchronous that yes, indeed, there's no
"single right way" to do it.

It is possible to get quite a bit of configuration work done, and
indeed, subscription requests submitted, before you start any of the
slon processes.

But for sure, for cascaded subscribers, you can't start *those*
subscriptions until the subscriptions that they depend on are active.
-- 
"cbbrowne","@","ca.afilias.info"
Christopher Browne
"Bother,"  said Pooh,  "Eeyore, ready  two photon  torpedoes  and lock
phasers on the Heffalump, Piglet, meet me in transporter room three"