On Mon, Sep 4, 2017 at 4:49 AM, Simon Riggs <si...@2ndquadrant.com> wrote: > 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 ...
Fair point. > 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." It's not really true that the only alternatives to pglogical are proprietary. Really, one could use any logical replication solution, and there have been multiple open source alternatives for a decade. > Our docs mention pglogical already, so don't see an issue with > mentioning it here. The existing reference is alongside a bunch of other third-party tools. Mentioning it at the very top of our release notes would give it a pride of place with which I'm not too comfortable. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
