Re: status/timeline of pglogical?

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Vik Fearing <vik(at)2ndquadrant(dot)fr>, 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-12 18:13:27
Message-ID: 5734C7C7.6000202@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

On 05/12/2016 07:37 AM, Robert Haas wrote:
> On Wed, May 11, 2016 at 7:10 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:

> 3. I think we need to replace pg_upgrade with a real in-place upgrade
> scheme so that you just fire up the new version of the server on your
> old data directory, and it rejiggers things in place without needing
> to create a new cluster and migrate stuff over to it. I think that
> actually making this work is a huge engineering effort, and I have no
> plans to undertake it in the near term, but I think it has to be done.
> pg_upgrade isn't reliable enough, and using pglogical means you need a
> second machine. Maybe everybody should run with a standby, but not
> everyone does.

I am not arguing with you but... good luck. History has shown that the
argument above is basically this:

https://en.wikipedia.org/wiki/Sisyphus

Sincerely,

JD

--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Damien Clochard 2016-05-12 18:13:34 Re: 20th anniversary posters
Previous Message Joshua D. Drake 2016-05-12 18:11:37 Re: When should be advocate external projects?