Re: Link to "Upgrading a PostgreSQL Cluster" in Release Notes
Magnus Hagander <magnus@hagander.net>
From: Magnus Hagander <magnus@hagander.net>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Vik Fearing <vik.fearing@2ndquadrant.com>,
Pg Docs <pgsql-docs@lists.postgresql.org>
Date: 2020-01-03T10:00:36Z
Lists: pgsql-docs
On Fri, Jan 3, 2020 at 9:57 AM Peter Eisentraut < peter.eisentraut@2ndquadrant.com> wrote: > 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 it makes sense to backpatch it. Lots of people still upgrade to at least 12 and 11, and that's a likely place for them to start reading. And if we're already covering 12 and 11, it is probably no big extra effort to do other supported branches as well. 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. > > +1. -- Magnus Hagander Me: https://www.hagander.net/ <http://www.hagander.net/> Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
Commits
-
doc: Add link to upgrading chapter to release notes
- 4c6f541a0aff 10.12 landed
- 676c9156bbc8 11.7 landed
- e05a3b490a25 12.2 landed