Re: Release Note changes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Release Note changes
Date: 2017-09-04 14:33:08
Message-ID: 22506.1504535588@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> Which is why next year when upgrading from PG10 -> PG11 we will
> mention it and that point not mention the other older solutions, which
> were once our best.

This is boilerplate text that we tend to copy-and-paste without thinking
about it; if it's designed in a way that requires it to change more than
about once per decade, that's going to be a problem. (The existing text
has been there verbatim since 9.0, looks like.)

I'm okay with a passing reference to some list of replication tools
elsewhere in the docs, but not with much more than that.

It's also worth pointing out that the existing wording is meant to
explain how to achieve upgrade-in-place. Logical replication to a
new server seems like a fundamentally different thing.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Arseny Sher 2017-09-04 14:41:19 DROP SUBSCRIPTION hangs if sub is disabled in the same transaction
Previous Message Bruce Momjian 2017-09-04 14:24:29 Re: GnuTLS support