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

[Andrew Sullivan]

When we designed Slony back in the day, the way to handle these “c can’t talk to a at all” cases was to use an offline mode that allowed snapshot application without ack notices going back and forth. But given the transitive path (a<->b<->c) I’m pretty sure the STORE PATH advice upthread is right. Been a long time though, and I’m working from memory. 

A

— 
Andrew Sullivan 
Please excuse my clumbsy thums

> On May 26, 2021, at 13:55, Richard Yen via Slony1-general <slony1-general at lists.slony.info> wrote:
> 
> 
> 
> 
>> On Wed, May 26, 2021 at 5:51 AM Sebastien Marchand <smarchand at sgo.fr> wrote:
>> Hi,
>> 
>> thank you, but i don't know how do this, my server A can't talk to my server C...
>> 
> Hi Sebastien,
> 
> Do you mean that you have not been able to get Server A to talk to Server C via Slony (but you can ping A from C), or do you mean that they are physically separated and there is no network path for A to talk to C, except via Server B?
> 
> If the latter is the case for you, then I think you will not be able to set up this kind of cascading replication, due to the session replication role I had mentioned in my earlier email (I actually tried to create a rudimentary patch to make it work, but I haven't yet figured out the details to actually pass QA [1])
> 
> If your case is the former (i.e., you can ping Server A from C), then I think Stéphane's suggestion should work for you
> 
> [1]: https://www.slony.info/pipermail/slony1-patches/2020-February/000123.html
> 
> --Richard
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slony.info/pipermail/slony1-general/attachments/20210526/738e0ea3/attachment-0001.htm>