On 10/09/2014 08:18 AM, Granthana Biswas wrote:
> Hi All,
>
> I am trying to replicate from another Slony cluster's slave node.
>
> Cluster1 -> replicating from DB1 to -> DB2
>
> Cluster2 -> replicating from DB2 to -> DB3
>
> The initial sync up went fine without any errors. There are no errors in
> logs of both the clusters. Also no st_lag_num_events in DB3 or DB2 for
> Cluster2.
>
> But the data added in DB2 since I started slony Cluster2 is not
> reflecting in DB3.
>
> Does slony allow replication from another cluster's slony slave? Or did
> I miss something?

This does not work because the logTrigger will only record information 
when firing in session_replication_role 'origin'. When Slony is applying 
changes from DB1 to DB2, the session_replication_role is 'replica', so 
the logTrigger action is suppressed inside the trigger function.

You will have to make DB3 a member of Cluster1 and use DB2 as the data 
provider to achieve this. This has the added benefit that you can easily 
change the data provider of DB3 to DB1 in case you need to perform any 
maintenance on DB2.


Regards,
Jan

-- 
Jan Wieck
Senior Software Engineer
http://slony.info