Re: A Modest Upgrade Proposal - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: A Modest Upgrade Proposal
Date
Msg-id 577EEA4C.60104@commandprompt.com
Whole thread Raw
In response to Re: A Modest Upgrade Proposal  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: A Modest Upgrade Proposal  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
On 07/07/2016 01:10 PM, Robert Haas wrote:
> On Mon, May 16, 2016 at 8:52 PM, David Fetter <david@fetter.org> wrote:
>> In light of the above, it is perfectly reasonable to require, at least
>> temporarily, setting up duplicate storage, or another node.

> pg_upgrade does that, kinda.  I'd like to have something better, but
> in the absence of that, I think it's quite wrong to think about
> deprecating it, even if we had logical replication fully integrated
> into core today.  Which we by no means do.

I would much rather see more brain power put into pg_upgrade or in place 
upgrades than logical replication (as a upgrade solution).

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.



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: pg_xlogfile_name_offset() et al and recovery
Next
From: Michael Paquier
Date:
Subject: Re: Issue with bgworker, SPI and pgstat_report_stat