Subject: Re: Link to "Upgrading a PostgreSQL Cluster" in Release Notes
To: Vik Fearing <vik.fearing@2ndquadrant.com>, pgsql-docs@lists.postgresql.org
References: <54c208b9-7e2c-6211-0ba0-ffb0429cf20b@2ndquadrant.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Organization: 2ndQuadrant
Message-ID: <2cfbd3fe-85ef-d53b-53db-d93fbfe9f578@2ndquadrant.com>
Date: Fri, 3 Jan 2020 09:57:10 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0)
 Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <54c208b9-7e2c-6211-0ba0-ffb0429cf20b@2ndquadrant.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Precedence: bulk

On 2019-12-30 00:03, Vik Fearing wrote:
> Following a complaint on IRC about the dearth of information on how to
> migrate to a new major version in the release notes, the attached
> trivial patch was determined to be sufficient for the OP.
> 
> This patch applies to REL_12_STABLE.  I don't know how far it should be
> backpatched (the OP was trying to upgrade to v10), and I didn't see any
> place to put it for 13 and future versions.

I think this change is sensible.  But to what extent do we want to edit 
around in old release notes?  Should we just keep it for PG13?

I think we should also extend the blurb in the release notes to mention 
the option of using logical replication to upgrade.  Otherwise, if you 
follow the link you propose, then one might think that logical 
replication upgrading is not applicable since only pg_dump and 
pg_upgrade were mentioned in the place the link came from.

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