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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-patches/attachments/20200220/6934bd70/attachment.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: support_logical_replication.patch
Type: application/octet-stream
Size: 495 bytes
Desc: not available
Url : http://lists.slony.info/pipermail/slony1-patches/attachments/20200220/6934bd70/attachment.obj