[Slony1-general] Replication cascade with 2 differents replications on the same table

[Steve Singer]

On Wed, 26 May 2021, Sebastien Marchand via Slony1-general wrote:

> 
> Hi,
> 
> thank you, but i don't know how do this, my server A can't talk to my server C...

I might misunderstand what your trying to do but does

store path(server=1, client=2, conninfo='serverA.local');
store path(server=2, client=1, conninfo='serverB.local');

store path(server=2, client=3, conninfo='serverB.local');
store path(server=3, client=2, conninfo='serverC.local');

subscribe set(id=1, provider=1, receiver=2, forward=yes);
subscribe set(id=1, provider=2, receiver=3, forward=yes);


where node 1=serverA, and node 2=serverB, node 3=serverC
work?

Slonik would need to be able to talk to all nodes.

Slon for serverB would need to be able to talk to all three servers.

Slon for serverA only needs to talk to server A and server B
Slon for serverC only needs to talk to server C and server B


Steve



> 
> Le 25/05/2021 à 23:23, Richard Yen a écrit :
> 
> 
> On Tue, May 25, 2021 at 3:11 AM Sebastien Marchand via Slony1-general <slony1-general at lists.slony.info> wrote:
>       I do this :
>
>       Server A -> Server  B -> Server C
>
>       _replication_N1 for server A to B and _replication _N2 server B to C on
>       the same table.
> 
>  
> If you are doing two replication sets, then this won't work.  That's because when data on Server A gets replicated to
> Server B, the replay on Server B is done with a replica identity that disables the triggers, which subsequently prevents
> replication to Server C.
> 
> If you want to do this replication architecture of A->B->C, then you will need C to subscribe to _replication_N1 and
> specify the source as Server B
> 
> Hope that helps!
> --Richard
> 
> 
>