Re: When should be advocate external projects? - Mailing list pgsql-advocacy

From Robert Haas
Subject Re: When should be advocate external projects?
Date
Msg-id CA+TgmoZXCLaH8gB_1greWyWMgKsCj2eJex1V_Bm+X2vWoY0LJg@mail.gmail.com
Whole thread Raw
In response to Re: When should be advocate external projects?  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: When should be advocate external projects?  (Petr Jelinek <petr@2ndquadrant.com>)
List pgsql-advocacy
On Thu, May 12, 2016 at 2:11 PM, Joshua D. Drake <jd@commandprompt.com> wrote:
> Agreed except under this definition:
>
> No other open source tool provides the solution.
>
> Right now for logical replication that uses the logical decoding API that
> PostgreSQL provides there is exactly "1" solution and that is PgLogical.
> That doesn't mean their aren't other Logical Replication solutions (Slony
> for example) but nobody in their right mind can say that Slony is the better
> choice for "standard master/slave" replication.

Well, this is exactly why it's hard to reach agreement on what should
be in a software catalog.  pglogical hit version 1.0 just 15 days ago,
and you're ready to say that anyone who thinks they might instead want
to use a tool that's been in production use for 10 years is crazy.
I'm going to say I disagree.  I do not believe people using pglogical
are crazy, and I don't believe people who are using Slony or Bucardo
or Londiste are crazy either.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-advocacy by date:

Previous
From: Gavin Flower
Date:
Subject: Re: New versioning scheme
Next
From: Robert Haas
Date:
Subject: Re: status/timeline of pglogical?