public inbox for [email protected]
help / color / mirror / Atom feedFrom: Magnus Hagander <[email protected]>
To: Peter Eisentraut <[email protected]>
Cc: Vik Fearing <[email protected]>
Cc: Pg Docs <[email protected]>
Subject: Re: Link to "Upgrading a PostgreSQL Cluster" in Release Notes
Date: Fri, 3 Jan 2020 11:00:36 +0100
Message-ID: <CABUevEwbaVZRANq_e9+wwgd_-Tbe2NP7O2zXeTnwJrLP2-ugcg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
On Fri, Jan 3, 2020 at 9:57 AM Peter Eisentraut <
[email protected]> 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/;
view thread (5+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: Link to "Upgrading a PostgreSQL Cluster" in Release Notes
In-Reply-To: <CABUevEwbaVZRANq_e9+wwgd_-Tbe2NP7O2zXeTnwJrLP2-ugcg@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox