public inbox for [email protected]  

help / color / mirror / Atom feed
From: Greg Sabino Mullane <[email protected]>
To: Vu Le (JData - HN) <[email protected]>
Cc: [email protected]
Subject: Re: Direct Major Upgrade (13.7 → 17.6) with pg_upgrade: Clarifying the need for Intermediate Minor Fixes/Scripts
Date: Wed, 1 Oct 2025 07:26:59 -0400
Message-ID: <CAKAnmm+1LZfutxkEcMxuXh-4WKyGxbS2cR+Ywi2crEk=yy1Ejw@mail.gmail.com> (raw)
In-Reply-To: <CACT9sojHVBtUjXe1uB7k6Fxp9ft_L2yUtAGL4JfkPWCXYW4A6w@mail.gmail.com>
References: <CACT9sojHVBtUjXe1uB7k6Fxp9ft_L2yUtAGL4JfkPWCXYW4A6w@mail.gmail.com>

On Wed, Oct 1, 2025 at 3:47 AM Vu Le (JData - HN) <[email protected]>
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
> 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


view thread (2+ 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]
  Subject: Re: Direct Major Upgrade (13.7 → 17.6) with pg_upgrade: Clarifying the need for Intermediate Minor Fixes/Scripts
  In-Reply-To: <CAKAnmm+1LZfutxkEcMxuXh-4WKyGxbS2cR+Ywi2crEk=yy1Ejw@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