Re: [HACKERS] Release Note changes - Mailing list pgsql-hackers

From Andreas Joseph Krogh
Subject Re: [HACKERS] Release Note changes
Date
Msg-id VisenaEmail.10.2d281e3a3f61da8f.15e4c395779@tc7-visena
Whole thread Raw
In response to [HACKERS] Release Note changes  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: [HACKERS] Release Note changes
List pgsql-hackers
På mandag 04. september 2017 kl. 10:49:40, skrev Simon Riggs <simon@2ndquadrant.com>:
Migration to Version 10

"A dump/restore using pg_dumpall, or use of pg_upgrade, is required
for those wishing to migrate data from any previous release."

This isn't true and is seriously misleading since pglogical and other
proprietary tools exist that were designed specifically to allow this.
Suggested additional wording would be...

"If upgrading from a 9.4 server or later, external utilities using
logical decoding, such as pglogical or proprietary alternatives, can
also provide an alternate route, often with lower downtime."

Our docs mention pglogical already, so don't see an issue with
mentioning it here.
 
I'd like at big red warning "Logical decoding doesn't support Large Objects" in that case;
 
"If upgrading from a 9.4 server or later, and you don't use Large Objects,
external utilities using logical decoding, such as pglogical or
proprietary alternatives, can also provide an alternate route,
often with lower downtime."
 
pg_upgrade or pg_dump is really the only option for us using LOs.
 
--
Andreas Joseph Krogh

pgsql-hackers by date:

Previous
From: Sokolov Yura
Date:
Subject: Re: [HACKERS] Proposal: pg_rewind to skip config files
Next
From: Amit Kapila
Date:
Subject: Re: [HACKERS] Parallel worker error