Re: Link to "Upgrading a PostgreSQL Cluster" in Release Notes
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Magnus Hagander <magnus@hagander.net>
Cc: Vik Fearing <vik.fearing@2ndquadrant.com>,
Pg Docs <pgsql-docs@lists.postgresql.org>
Date: 2020-01-09T15:19:44Z
Lists: pgsql-docs
On 2020-01-03 11:00, Magnus Hagander 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. Committed to 12, 11, 10. After that the patch didn't apply anymore and nobody should be upgrading to that anyway. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
doc: Add link to upgrading chapter to release notes
- 4c6f541a0aff 10.12 landed
- 676c9156bbc8 11.7 landed
- e05a3b490a25 12.2 landed