Re: status/timeline of pglogical?

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Martín Marqués <martin(at)2ndquadrant(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Joshua Drake <jd(at)commandprompt(dot)com>, Vik Fearing <vik(at)2ndquadrant(dot)fr>, Josh berkus <josh(at)agliodbs(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Dave Page <dpage(at)pgadmin(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-advocacy <pgsql-advocacy(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: status/timeline of pglogical?
Date: 2016-05-13 17:59:47
Message-ID: 20160513175947.GA3267@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

On Fri, May 13, 2016 at 01:48:39PM -0300, Martín Marqués wrote:
> El 12/05/16 a las 12:26, Magnus Hagander escribió:
> > Can it be made to work? Sure. But I definitely agree with Robert that we
> > need "real" in place upgrades at some point.
>
> It would be a neat feature. The question is if there will be such a
> solution and if it will be or not reliable.

My point is that it will require major changes/testing for _every_ major
release because there would be substantial upgrade-only code needed for
every major release. This is not true for pg_upgrade, and avoiding this
is part of its design.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Josh berkus 2016-05-13 18:01:27 Re: When should be advocate external projects?
Previous Message Peter Geoghegan 2016-05-13 17:58:01 Re: 20th anniversary posters