Le 27/05/2021 à 10:05, Sebastien Marchand via Slony1-general a écrit : > Hi, > > I will try this today. > > I can move slon from A to B too no ? Result, 2 slon on B , one on C and no > one on A. > > Thank you all > You can have your 3 slon daemons running on B, which can see all nodes, indeed.
That will simplify slon management. > > Le 27/05/2021 à 03:50, Steve Singer a écrit : >> 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@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 >>> >>> >>> > _______________________________________________ > Slony1-general mailing list > Slony1-general@lists.slony.info > http://lists.slony.info/mailman/listinfo/slony1-general -- Dr Stéphane Schildknecht Contact régional PostgreSQL pour l'Europe francophone +33 617 11 37 42
_______________________________________________ Slony1-general mailing list Slony1-general@lists.slony.info http://lists.slony.info/mailman/listinfo/slony1-general
