Shaun Thomas sthomas
Wed Nov 29 16:20:31 PST 2006
This is probably due to me doing something stupid, but I figured I'd ask
anyway.

I've got a configuration that looks roughly like this:

Node 1 - schema foo, host foo, master of set 1
Node 2 - schema bar, host foo, master of set 2
Node 3 - schema foo + schema bar, host baz, wants set 1 and 2.

Node 1, set 1 -> Node 3 = works fine.
Node 2, set 2 -> Node 3 = el nada.

The idea here is that I have two schemas on different postgresql
logical databases on another machine I'm combining into a single logical
database so I can actually access all of the tables in a single query. 
There's no table overlap, and each set is self-contained on the node
defined as the set provider.

>From sl_status, it looks like node 3 is either not receiving or not
acknowledging the SYNCs from node 2.  I've got six entries in sl_paths
and ten in sl_path, and I see 6 slon processes running for all the
nodes.  What I don't get is why node3 isn't liking node 2.

Am I bending slony too far by wanting one node to subscribe to two
sets?  Should I create two separate replication installs to resolve
this?

Thanks!

Confidentiality Note:

The document(s) accompanying this e-mail transmission, if any, and the
e-mail transmittal message containing information from Leapfrog Online
Customer Acquisition, LLC is confidential or privileged. The information
is intended to be for the use of the individual(s) or entity(ies) named
on this e-mail transmission message. If you are not the intended
recipient, be aware that any disclosure, copying, distribution or use of
the contents of this e-mail is prohibited. If you have received this
e-mail in error, please immediately delete this e-mail and notify us by
telephone of the error



More information about the Slony1-general mailing list