On Thu, Sep 08, 2005 at 01:26:40AM -0400, Jim Archer wrote:
> Christopher Browne said:
> 
> > No, the "expected result" of submitting "that command" to a node
> > already participating in a subscription is for the subscription
> > provider to be revised.
> >
> > Thus, you might start with...
> >
> >     A ---> B ----> C
> >
> > And revise it to...
> >
> >     A ---> B
> >       \
> >        \
> >         \> C
> >
> > If you request a 'path' that is already in effect, it'll turn out as a
> > NOOP.
> >
> > What you could do to accomplish what I think you want to do is to
> > submit "*UN*S*U*B****** SET."
> 
> I just gave this a try.  I rebuilt my cluster from scratch and had a 2
> machine cluster.  I issued:
> 
> unsub*scr*ibe set (id = @SET_FULL, receiver = @NODE_02);
> 
> This seemed to work as documented.  The database on the slave was
> unlocked, so I could modify it, and the slony-added schema remained in
> place.
> 
> I then issued:
> 
> sub*scr*ibe set (id = @SET_FULL, provider = @ORIGIN, receiver = @NODE_02,
> forward = no );
> 
> That didn't seem to do anything.  The database remained unlocked and I
> didn't see any copy activity in the slon log that services that node.
> 
> I then decided to add a third node to the cluster.  I issued:
> 
> store node (id=@NODE_04, comment = 'Node 04 Hartford', spoolnode=false,
> event node = @ORIGIN);
> 
> This created the schema on that node correctly.  I then started a slon to
> service this new node and issued:
> 
> subscribe set ( id = @SET_FULL, provider = @ORIGIN, receiver = @NODE_04,
> forward = no);
> 
> Again, nothing.  No copy activity.
> 
> Oh, I created the store paths when I created the cluster originally.
> 
> Did I miss something or is there a problem with subscribing sets on an
> existing cluster?

It may be worth looking at sl_node, sl_subscribe, sl_path, and sl_listen
(in the slony schema) on all of the nodes to see what's gotten through 
and what hasn't. You've issued a few slonik commands now that haven't
propogated, and you need to see if anything's gotten through to all of the 
nodes. 

Often, if you're sending events through and they're not showing up on
all of the nodes, it's one of the following:

1. A slon isn't running
2. Your paths are wrong
3. Your listen network is wrong
4. You haven't waited long enough for the event to propogate through to
all of the nodes

 
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/slony1-general

-- 
Tim Goodaire    416-673-4126    tgoodair at ca.afilias.info
Database Administrator, Afilias Canada Corp.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://gborg.postgresql.org/pipermail/slony1-general/attachments/20050908/839350e5/attachment.bin