Re: Link to "Upgrading a PostgreSQL Cluster" in Release Notes

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com>, Pg Docs <pgsql-docs(at)lists(dot)postgresql(dot)org>
Subject: Re: Link to "Upgrading a PostgreSQL Cluster" in Release Notes
Date: 2020-01-09 15:19:44
Message-ID: b8f55d78-e4be-cbe8-53a0-6f7a4340c0ad@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Stephen Frost 2020-01-09 17:00:24 Re: Postgres.js driver - for Node.js
Previous Message Tom Lane 2020-01-09 13:57:54 Re: Typo in Documentation for Version 12 Section 40.3