Re: When should be advocate external projects?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org>
Subject: Re: When should be advocate external projects?
Date: 2016-05-13 14:55:09
Message-ID: CA+TgmoZXCLaH8gB_1greWyWMgKsCj2eJex1V_Bm+X2vWoY0LJg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

On Thu, May 12, 2016 at 2:11 PM, Joshua D. Drake <jd(at)commandprompt(dot)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

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Robert Haas 2016-05-13 14:57:48 Re: status/timeline of pglogical?
Previous Message Gavin Flower 2016-05-13 13:21:49 Re: New versioning scheme