Re: status/timeline of pglogical?

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Vik Fearing <vik(at)2ndquadrant(dot)fr>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Dave Page <dpage(at)pgadmin(dot)org>, Josh berkus <josh(at)agliodbs(dot)com>, pgsql-advocacy <pgsql-advocacy(at)postgresql(dot)org>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>
Subject: Re: status/timeline of pglogical?
Date: 2016-05-11 23:10:06
Message-ID: CANP8+jKTN2xD2n46vPskkGkEME1+G0y=9f1z6S5UdMm8o9P=-A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

On 11 May 2016 at 23:40, Bruce Momjian <bruce(at)momjian(dot)us> wrote:

> I encourage mentioning external tools in the right context --- we need
> more of that.

Good to know.

I think the question is whether a beta announcement is
> the right place for external tool announcements.
>

The only reason this has been brought up is that pglogical is a tool
designed to reduce the impact of upgrades. No other tool has ever been
available externally to do that, apart from pg_upgrade which was accepted
into core in quite a poor state. So this discussion has not been about
"external tools" it has been about the one and only external tool that
provides an improved upgrade route.

If people don't want to mention it, fine, no problem, as I said I've not
sought to create a new precedent.

We can add some mentions in the docs in appropriate locations, for example,
the detailed release notes and upgrade pages.

--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Bruce Momjian 2016-05-11 23:16:41 Re: status/timeline of pglogical?
Previous Message Bruce Momjian 2016-05-11 22:40:20 Re: status/timeline of pglogical?