Release Note changes

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Release Note changes
Date: 2017-09-04 08:49:40
Message-ID: CANP8+j+Rgod5M_DcD91OjxzaYsZVF8NLhncRjt5R4hj34o+k4g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Chris Travers 2017-09-04 08:53:15 Proposal: pg_rewind to skip config files
Previous Message Christoph Berg 2017-09-04 08:22:12 Re: initdb failure on Debian sid/mips64el in EventTriggerEndCompleteQuery