public inbox for pgsql-admin@postgresql.org
help / color / mirror / Atom feedFrom: Ron Johnson <ronljohnsonjr@gmail.com>
To: 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 11:37:25 -0400
Message-ID: <CANzqJaDnQnQnv-Ya2j5xT+rxpgsV9=7+jgGJab+eznsu2+ba-Q@mail.gmail.com> (raw)
In-Reply-To: <CACGXUKhSCXyKyfebbgzU=vb7O7=xMVRYn3gywoXyYJeUXvUALg@mail.gmail.com>
References: <CACGXUKhSCXyKyfebbgzU=vb7O7=xMVRYn3gywoXyYJeUXvUALg@mail.gmail.com>
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.
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
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: 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: <CANzqJaDnQnQnv-Ya2j5xT+rxpgsV9=7+jgGJab+eznsu2+ba-Q@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