On Jul 16, 2004, at 3:55 PM, Christopher Browne wrote:

> I think you're confusing here:
>  - Where do I run slonik, which talks to database instances, and
>    tells them how to control what's going on?
>
>    Slonik should be able to run anywhere that can talk to one or more
>    of the DBs; it initiates connections to the databases based on the
>    conninfo strings you pass in.

So there's a slonik script for setting up and a slonik script for 
subscribing. The way I understood it from reading the docs is that this 
is the general procedure:

1. Set up a schema on the slave node based on the master.
2. Run a slonik configuration script.
3. Run slon on both master and slave.
4. Run a slonik subscription script.

>  - Where do I run slon, which is the daemon that controls a particular
>    replication instance?
>
>    The initial assumption was that that should run on the DB server.

By DB server, do you mean master node?

> After some experimenting this week, it turns out that it doesn't
> matter TOO much where slon instances run, as long as origins and
> subscribers are on a local network.

Oh, I was under the impression that the slon daemon need to be running 
on any server that was acting as a node.

> By the way, I'll Real Soon Now be putting into CVS a set of Perl
> scripts that represent a somewhat more sophisticated set of
> functionality:
>
>  - They support having a whole "tree" of Slony-I nodes, not just
>    a 'master' and a 'slave.'
>  - There are separate scripts for the many actions you might want
>    to perform.  Initializing, re-initializing, adding sets,
>    adding subscribers, and such.

Sounds good.

-tfo