On 10/16/2013 09:17 AM, Sebastien Marchand wrote:
> Hi,
>
> I want do this :
>
> SERVER 1			SERVER 2
> SCHEMA A	------->		SCHEMA A
> SCHEMA B	<-------		SCHEMA B
>
> That works in slony 2.0.7/pg 9.0
>
> But with  slony 2.2 and postgresql 9.3
>
> SERVER 1			SERVER 2	
> SCHEMA A	------->		SCHEMA A	=> OK
> SCHEMA B	<-------		SCHEMA B	=> NOK
>
> I've got this error
>
> <stdin>:55: waiting for event (101,5000000004) to be  confirmed on node 110
>
> Pg error :
>
> 2013-10-15 10:55:10.950 CEST >ERROR:  relation
> "_sloncluster.sl_local_node_id" does not exist at character 30
> 2013-10-15 10:55:10.950 CEST >STATEMENT:  select last_value::int4 from
> "_sloncluster".sl_local_node_id
>
> Sorry for my english... :(
>

The way you would do this is with two replication sets

clustername=sloncluster;
node 1 admin conninfo=.....
node 2 admin conninfo=.....

init cluster(id=1);
store node(id=2, event node=2);
store path(server=1,client=2,conninfo=....);
store path(server=2,client=1,conninfo=.....);

create set(id=1,origin=1);
set add table(set id=1, tables='schemaA\.*');
create set(id=2, origin=2);
set add table(set id=1, tables='schemaB\.*');

subscribe set(set id=1, provider,1,receiver=2);
sync(id=1);
wait for event(origin=1, wait on=1,confirmed=2);
subscribe set(set id=2, provider=2,receiver=1);
sync(id=2);
wait for event(origin=2,wait on=2,confirmed=1);


or something similiar to above should work the same in 2.1 and 2.2  (in 
2.0 you would need explicit 'set add table' statements for each table 
and maybe a few more 'wait for event' statements in the middle of the 
script).

Are you doing something significantly different?