Thank you all for the answers. We'll proceed with this approach most likely.

> If you're using Slony, you might as well go to 9.6.latest while you're
at it.

Unfortunately, we won't be able to upgrade straight away. We have to take this environment one step at the time.
Though, now that you mentioned data loss bugs  we might speed it up and look into specifics more.

Thanks again!
Zarko


________________________________
From: slony1-general-bounces at lists.slony.info <slony1-general-bounces at lists.slony.info> on behalf of David Fetter <david at fetter.org>
Sent: Thursday, February 23, 2017 7:00 PM
To: slony1-general at lists.slony.info
Subject: Re: [Slony1-general] Slony and streaming replication combo

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/
David Fetter's Resume<http://fetter.org/>
fetter.org
DAVID FETTER. 3250 West St Oakland, CA 94608-4330 phone: 415-235-3778 e-mail: david at fetter.org TripIt Calendar Feed. Computer Skills. Database Development and ...



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 at lists.slony.info
http://lists.slony.info/mailman/listinfo/slony1-general
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20170224/df440289/attachment.htm