________________________________
> From: Granthana Biswas <granthana.biswas at gmail.com>
>To: "slony1-general at lists.slony.info" <slony1-general at lists.slony.info> 
>Sent: Thursday, 9 October 2014, 14:19
>Subject: [Slony1-general] Error with Slony replication from another slony cluster slave
> 
>
>
>Hi Glyn,
>
>
>
>I am trying to set up a totally separate cluster for DB2 -> DB3  :
>
>Cluster1 -> replicating from DB1 to -> DB2
>
>
>Cluster2 -> replicating from DB2 to -> DB3
>
>
>Granthana
>
>

As Jan has already stated, it's not possible to do this with 2 separate clusters because the logtriggers won't fire on DB2 due to the session replication role.

You want to get rid of Cluster2 and subscribe DB3 into Cluster1 with DB2 as it's provider.


>On Thu, Oct 9, 2014 at 6:10 PM, Glyn Astill <glynastill at yahoo.co.uk> wrote:
>
>
>>
>>
>>
>>
>>>________________________________
>>> From: Granthana Biswas <granthana.biswas at gmail.com>
>>>To: slony1-general at lists.slony.info
>>>Sent: Thursday, 9 October 2014, 13:18
>>>Subject: [Slony1-general] Error with Slony replication from another slony    cluster slave
>>
>>>
>>>
>>>
>>>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?
>>>
>>>
>>
>>Perhaps you could show us what you've done so far, to me it's unclear if you are setting up a totally seperate slony cluster for DB2->DB3, or just trying to subscribe DB3 to sets in the existing cluster.
>>
>>
>>If it's the latter, then as long as the slave you want to use as the provider was subscribed to the sets you want with "FORWARD = YES" it should be ok
>>
>>
>>See: http://main.slony.info/documentation/stmtsubscribeset.html
>>
>>You should be able to check by looking at sub_forward in sl_subscribe, some thing like:
>>
>>select * from _<cluster name>.sl_subscribe where sub_receiver = <id of DB2>;
>>
>>
>>>Thanks & Regards,
>>>Granthana Biswas