On Thu, 20 Feb 2020, Richard Yen wrote:

So with your patch, what happens on node C?
Do the replication triggers fire there as well?



> I recently came across a customer who sought to set up Slony on the tail end of a cascaded-replication
> setup:
> Node A -> Logical Replication -> Node B -> Slony -> Node C
> 
> We discovered that this does not work because the client (WAL replay process) logs in as a Replica user,
> but logTrigger won't fire unless replication role is Origin.
> 
> Seeing that the "replication role == Origin" check is a bit dated, and Slony will enable/disable triggers
> based on subscriber/provider status, I'm thinking that the attached patch might be worth a discussion. 
> After all, the "replication role == Origin" check basically negates all the replication role features
> that are now baked into Postgres core.
> 
> Please let me know if there are other factors to consider.
> 
> Cheers,
> --Richard
> 
> 
> 
>