On Wed, Feb 22, 2017 at 05:30:43PM +0000, 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).
> "New B" (disaster recovery site) <---- Streaming replication ---- "New A" > <--------Slony replication ----- "Old A" ------ existing SR ------> "Old B" > (DR site) I can see no reason it wouldn't work. Slony does things that are pretty much disjoint from what streaming replication does, so they won't be able to ste on each others' toes. > 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. If you're using Slony, you might as well go to 9.6.latest while you're at it. You won't save time by replicating yet again to another virtual server, and the chances that going to 9.6 will break something are much smaller than the chances that staying on the now-defunct 9.1 will. There have already been data loss bugs that were fixed since 9.1 went out of support, i.e. 9.1 didn't get those fixes applied. That setup will work nicely with what I hope will become a routine operation, namely upgrading major versions. :) Best, David. -- David Fetter <david(at)fetter(dot)org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate _______________________________________________ Slony1-general mailing list Slony1-general@lists.slony.info http://lists.slony.info/mailman/listinfo/slony1-general
