public inbox for pgsql-admin@postgresql.org  

help / color / mirror / Atom feed

From: Robert Treat <rob@xzilla.net>
To: Ron Johnson <ronljohnsonjr@gmail.com>
Cc: Balaji Ram <balajiram.ganesan@gmail.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Pg upgrade from 13.20 to 17.9
Date: Mon, 30 Mar 2026 15:26:27 -0400
Message-ID: <CABV9wwO0y8ew8_O6edT67UnQ07+NBeDueDQ6BF=zWFd0VUiVhA@mail.gmail.com> (raw)
In-Reply-To: <CANzqJaDnQnQnv-Ya2j5xT+rxpgsV9=7+jgGJab+eznsu2+ba-Q@mail.gmail.com>
References: <CACGXUKhSCXyKyfebbgzU=vb7O7=xMVRYn3gywoXyYJeUXvUALg@mail.gmail.com>
	<CANzqJaDnQnQnv-Ya2j5xT+rxpgsV9=7+jgGJab+eznsu2+ba-Q@mail.gmail.com>

On Mon, Mar 30, 2026 at 11:37 AM Ron Johnson <ronljohnsonjr@gmail.com> wrote:
> On Mon, Mar 30, 2026 at 4:16 AM Balaji Ram <balajiram.ganesan@gmail.com> wrote:
>>
>> Hi Everyone,
>>
>> I'm planning to upgrade a standalone PostgreSQL cluster from **13.20 to 17.9**. I haven’t performed a major version upgrade with such a large version gap before, so I’d appreciate any guidance on best practices, recommended approaches, and things to watch out for.
>
>
> 1. Read the PG 14, 15, 16 and 17 release notes.
> 2. Being on the latest is the latest release (in this case, 13.23) is always Best Practice.
>

+1 to the above, pay special attention to any incompatibilities
information. If you want to be really thorough, you should look at the
first few minor release for each branch to see if there are any system
catalog updates or reindexing type activities you need to deal with.

Also, if you have any extensions, you'll need to verify that those
will also survive such a big version jump; there's an outside chance
you may need to stop at some major version along the way.

Oh. and if you don't have a strong reason against it, most would
probably recommend you go to v18 at this point.


Robert Treat
https://xzilla.net

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: pgsql-admin@postgresql.org
  Cc: rob@xzilla.net, ronljohnsonjr@gmail.com, balajiram.ganesan@gmail.com, pgsql-admin@lists.postgresql.org
  Subject: Re: Pg upgrade from 13.20 to 17.9
  In-Reply-To: <CABV9wwO0y8ew8_O6edT67UnQ07+NBeDueDQ6BF=zWFd0VUiVhA@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