MIME-Version: 1.0
References: <CACT9sojHVBtUjXe1uB7k6Fxp9ft_L2yUtAGL4JfkPWCXYW4A6w@mail.gmail.com>
 <CAKAnmm+1LZfutxkEcMxuXh-4WKyGxbS2cR+Ywi2crEk=yy1Ejw@mail.gmail.com>
In-Reply-To: <CAKAnmm+1LZfutxkEcMxuXh-4WKyGxbS2cR+Ywi2crEk=yy1Ejw@mail.gmail.com>
From: "Vu Le (JData - HN)" <dba4@jprotech.com.vn>
Date: Wed, 1 Oct 2025 21:14:56 +0700
Message-ID: <CACT9sogeiw2SdHS-=BqS2j-BVf5GcDhjByHOtjc4cBcz95uc_w@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: Greg Sabino Mullane <htamfids@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CACT9sogeiw2SdHS-%3DBqS2j-BVf5GcDhjByHOtjc4cBcz95uc_w%40mail.gmail.com>
Precedence: bulk

Hi Greg,
Much appreciated for the clear confirmation! It=E2=80=99s great to know tha=
t
`pg_upgrade` takes care of all structural changes, and that the
remaining "extra works" are indeed a rare manual check. I will follow
your advice and use common sense during the final review. Thanks for
the guidance and the reassurance.


On Wed, Oct 1, 2025 at 6:27=E2=80=AFPM Greg Sabino Mullane <htamfids@gmail.=
com> wrote:
>
> On Wed, Oct 1, 2025 at 3:47=E2=80=AFAM Vu Le (JData - HN) <dba4@jprotech.=
com.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 extra w=
orks/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 abov=
e, it's a manual step of reading the release notes and taking steps dependi=
ng on your particular database. Keep in mind, these steps are very rare.
>
>> Does pg_upgrade implicitly incorporate all necessary structural fixes fr=
om the minor versions between 13.7 and 17.6?
>
>
> Yes
>
>>
>> Has anyone in the community performed a similar large jump and found une=
xpected 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
>


--=20
Best Regards,

Miles Le (Mr.)