MIME-Version: 1.0
References: <54c208b9-7e2c-6211-0ba0-ffb0429cf20b@2ndquadrant.com>
 <2cfbd3fe-85ef-d53b-53db-d93fbfe9f578@2ndquadrant.com>
In-Reply-To: <2cfbd3fe-85ef-d53b-53db-d93fbfe9f578@2ndquadrant.com>
From: Magnus Hagander <magnus@hagander.net>
Date: Fri, 3 Jan 2020 11:00:36 +0100
Message-ID: 
 <CABUevEwbaVZRANq_e9+wwgd_-Tbe2NP7O2zXeTnwJrLP2-ugcg@mail.gmail.com>
Subject: Re: Link to "Upgrading a PostgreSQL Cluster" in Release Notes
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Vik Fearing <vik.fearing@2ndquadrant.com>,
 Pg Docs <pgsql-docs@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000004b296d059b396268"
Precedence: bulk

--0000000000004b296d059b396268
Content-Type: text/plain; charset="UTF-8"

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/>

--0000000000004b296d059b396268
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jan 3, 2020 at 9:57 AM Peter =
Eisentraut &lt;<a href=3D"mailto:peter.eisentraut@2ndquadrant.com">peter.ei=
sentraut@2ndquadrant.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex">On 2019-12-30 00:03, Vik Fearing wrote:<br>
&gt; Following a complaint on IRC about the dearth of information on how to=
<br>
&gt; migrate to a new major version in the release notes, the attached<br>
&gt; trivial patch was determined to be sufficient for the OP.<br>
&gt; <br>
&gt; This patch applies to REL_12_STABLE.=C2=A0 I don&#39;t know how far it=
 should be<br>
&gt; backpatched (the OP was trying to upgrade to v10), and I didn&#39;t se=
e any<br>
&gt; place to put it for 13 and future versions.<br>
<br>
I think this change is sensible.=C2=A0 But to what extent do we want to edi=
t <br>
around in old release notes?=C2=A0 Should we just keep it for PG13?<br></bl=
ockquote><div><br></div><div>I think it makes sense to backpatch it. Lots o=
f people still upgrade to at least 12 and 11, and that&#39;s a likely place=
 for them to start reading. And if we&#39;re already covering 12 and 11, it=
 is probably no big extra effort to do other supported branches as well.</d=
iv><div><br></div><div><br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex">
I think we should also extend the blurb in the release notes to mention <br=
>
the option of using logical replication to upgrade.=C2=A0 Otherwise, if you=
 <br>
follow the link you propose, then one might think that logical <br>
replication upgrading is not applicable since only pg_dump and <br>
pg_upgrade were mentioned in the place the link came from.<br><br></blockqu=
ote></div><div><br></div><div>+1.<br></div><div><br></div>-- <br><div dir=
=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr"><div>=C2=A0Magnus Hagan=
der<br>=C2=A0Me: <a href=3D"http://www.hagander.net/" target=3D"_blank">htt=
ps://www.hagander.net/</a><br>=C2=A0Work: <a href=3D"http://www.redpill-lin=
pro.com/" target=3D"_blank">https://www.redpill-linpro.com/</a></div></div>=
</div></div>

--0000000000004b296d059b396268--