From: | Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | 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 18:22:00 |
Message-ID: | c57af416-0a24-f303-e4f5-4417c9f88dfe@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On 09/01/2020 16:19, Peter Eisentraut wrote:
> 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.
>
Thanks! And thanks for adding the logical replication text, too.
--
Vik Fearing
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2020-01-10 00:40:54 | Re: SE-Linux mispelled |
Previous Message | Stephen Frost | 2020-01-09 17:00:24 | Re: Postgres.js driver - for Node.js |