MIME-Version: 1.0
References: <CACT9sojHVBtUjXe1uB7k6Fxp9ft_L2yUtAGL4JfkPWCXYW4A6w@mail.gmail.com>
In-Reply-To: <CACT9sojHVBtUjXe1uB7k6Fxp9ft_L2yUtAGL4JfkPWCXYW4A6w@mail.gmail.com>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Wed, 1 Oct 2025 07:26:59 -0400
Message-ID: <CAKAnmm+1LZfutxkEcMxuXh-4WKyGxbS2cR+Ywi2crEk=yy1Ejw@mail.gmail.com>
Subject: =?UTF-8?Q?Re=3A_Direct_Major_Upgrade_=2813=2E7_=E2=86=92_17=2E6=29_with_pg=5Fupg?=
	=?UTF-8?Q?rade=3A_Clarifying_the_need_for_Intermediate_Minor_Fixes=2FScrip?=
	=?UTF-8?Q?ts?=
To: "Vu Le (JData - HN)" <dba4@jprotech.com.vn>
Cc: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000c29f5e06401727b4"
Archived-At: <https://www.postgresql.org/message-id/CAKAnmm%2B1LZfutxkEcMxuXh-4WKyGxbS2cR%2BYwi2crEk%3Dyy1Ejw%40mail.gmail.com>
Precedence: bulk

--000000000000c29f5e06401727b4
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Oct 1, 2025 at 3:47=E2=80=AFAM Vu Le (JData - HN) <dba4@jprotech.co=
m.vn>
wrote:

> My question is: When performing a direct jump from 13.7 to 17.6 using
> pg_upgrade, do I need to manually identify and execute the cumulative ext=
ra
> works/fixes from ALL the skipped intermediate versions (13.8, 13.9, 14.x,
> 15.x, 16.x)?
>

Yes. Although with common sense, e.g. no need to reindex something twice.

Is there an official best practice document that clarifies how
> pg_upgrade handles these "extra works" from skipped minor releases?
>

These are not handled by pg_upgrade, hence the "extra". As you noted above,
it's a manual step of reading the release notes and taking steps depending
on your particular database. Keep in mind, these steps are very rare.

Does pg_upgrade implicitly incorporate all necessary structural fixes from
> the minor versions between 13.7 and 17.6?
>

Yes


> Has anyone in the community performed a similar large jump and found
> unexpected issues due to skipping these intermediate manual steps?
>

I've jumped many versions, many times, for many clients. Just follow the
recommended steps and all will be well.

Cheers,
Greg

--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support

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

<div dir=3D"ltr"><div dir=3D"ltr">On Wed, Oct 1, 2025 at 3:47=E2=80=AFAM Vu=
 Le (JData - HN) &lt;<a href=3D"mailto:dba4@jprotech.com.vn">dba4@jprotech.=
com.vn</a>&gt; wrote:</div><div class=3D"gmail_quote gmail_quote_container"=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex">My question is: When per=
forming a direct jump from 13.7 to 17.6 using pg_upgrade, do I need to manu=
ally identify and execute the cumulative extra works/fixes from ALL the ski=
pped intermediate versions (13.8, 13.9, 14.x, 15.x, 16.x)?<br></blockquote>=
<div><br></div><div>Yes. Although with common sense, e.g. no need to reinde=
x something twice.</div><div><br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex">Is there an official best practice document that clarifies ho=
w<br>
pg_upgrade handles these &quot;extra works&quot; from skipped minor release=
s?<br></blockquote><div><br></div><div>These are not handled by pg_upgrade,=
 hence the &quot;extra&quot;. As you noted above, it&#39;s a manual step of=
 reading the release notes and taking steps depending on your particular da=
tabase. Keep in mind, these steps are very rare.</div><div><br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex">
Does pg_upgrade implicitly incorporate all necessary structural fixes from =
the minor versions between 13.7 and 17.6?<br></blockquote><div><br></div><d=
iv>Yes</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex">
Has anyone in the community performed a similar large jump and found unexpe=
cted issues due to skipping these intermediate manual steps?<br></blockquot=
e><div><br></div><div>I&#39;ve jumped many versions, many times, for many c=
lients. Just follow the recommended steps and all will be well.</div></div>=
<div><br></div><div>Cheers,</div><div dir=3D"ltr" class=3D"gmail_signature"=
><div dir=3D"ltr"><div>Greg</div><div><br></div><div>--</div><div>Crunchy D=
ata - <a href=3D"https://www.crunchydata.com" target=3D"_blank">https://www=
.crunchydata.com</a></div><div>Enterprise Postgres Software Products &amp; =
Tech Support</div><div><br></div></div></div></div>

--000000000000c29f5e06401727b4--