You can specify that in the store path like this:
store path (server = 1, client = 2, conninfo = 'dbname=$DB host=$Node1
user=$U');
store path (server = 2, client = 1, conninfo = 'dbname=$DB host=$Node2
user=$U');

#store path (server = 2, client = 3, conninfo = 'dbname=$DB host=$Node2
user=$U');
#store path (server = 3, client = 2, conninfo = 'dbname=$DB host=$Node3
user=$U');

and do subscribe to Node that you want it to subscribe. (ex. subscribe set
(id = 1, provider = 1, receiver = 2, forward = no); and/or subscribe set (id
= 1, provider = 3, receiver = 4, forward = no);

In this case, Node 1 only communicate with node 2 and node 3 with node 4. 

But if you want all 4 nodes be able to commnicate to eachother and only
these two tables stays within their "local" then you can do that on
subscribe sets to nodes you want. ex. subscribe set (id = (your table id),
provider = 1, receiver = 2, forward = no)

Steven Huang



michael-539 wrote:
> 
> Hi everyone, I've got a situation I need some help with. I have a group
> of 4 servers - two in one city and two in another. There's about 45
> tables, most of which can be replicated through the whole set without
> any issue. I have two tables that I want replicated from Node 1-2 and
> Node 3-4, but I do not want replicated from 1-3 or 2-3. Basically, each
> city needs to have its own data for these two tables and the data should
> only be replicated between nodes in the same city. 
> 
>  
> 
> It seems to me that I can't have one table in two sets, even if it uses
> different origin nodes. Any tips?
> 
> 
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
> 
> 

-- 
View this message in context: http://www.nabble.com/Replicating-1-table-from-various-sources-tp25283718p25466502.html
Sent from the Slony-I -- General mailing list archive at Nabble.com.