I've done this. It works fine.

Make sure you install the slony extensions on Old B and New B in the event you need to fail over to one of the B nodes.


> On Feb 22, 2017, at 6:52 PM, Steve Singer <steve at ssinger.info> wrote:
> 
> I can't think why it wouldn't work. You should be able to do streaming replication from a slony subscriber.
> 
> I have not tried a similar setup myself
> 
> Zarko Aleksic wrote:
>> Greetings everyone,
>> 
>> We've recently started considering Slony for purpose of migrating PostgreSQL from old physical server to a new virtualized and "updated" platform. So far, all our tests worked quite well. However, I'm having trouble finding any documentation to prove or disprove that the following scenario is supported and/or will work properly (initial testing was positive though).
>> 
>> We would like to setup streaming replication between future Slony subscriber and our DR site beforehand, ie. before we introduce Slony. This would save us time and additional work post migration. 
>> 
>> It would look something like this:
>> "New B" (disaster recovery site)   <---- Streaming replication ----  "New A" <--------Slony replication ----- "Old A"  ------ existing SR ------> "Old B" (DR site)
>> Streaming replication between "New A" and "New B" would be setup first
>> Then we would setup Slony replication between "Old A" and "New A"
>> Slony replication Set would be moved from "Old A" to "New A"
>> Slon process would be stopped and Slony Schema would be removed 
>> Has anyone done something similar? Are there potential downsides to this idea? 
>> 
>> We are using slony1-91-II-2.1.4 and Postgres 9.1 on RHEL 6, later we will most likely do the same type of migration from 9.1 to 9.5. 
>> 
>> Any response is greatly appreciated.
>> Thanks!
>> Zarko
>> 
> Sent Using Firefox OS
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info <mailto:Slony1-general at lists.slony.info>
> http://lists.slony.info/mailman/listinfo/slony1-general <http://lists.slony.info/mailman/listinfo/slony1-general>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20170222/170cfbdc/attachment.htm