MIME-Version: 1.0
References: 
 <CACGXUKhSCXyKyfebbgzU=vb7O7=xMVRYn3gywoXyYJeUXvUALg@mail.gmail.com>
In-Reply-To: 
 <CACGXUKhSCXyKyfebbgzU=vb7O7=xMVRYn3gywoXyYJeUXvUALg@mail.gmail.com>
From: Ron Johnson <ronljohnsonjr@gmail.com>
Date: Mon, 30 Mar 2026 11:37:25 -0400
Message-ID: 
 <CANzqJaDnQnQnv-Ya2j5xT+rxpgsV9=7+jgGJab+eznsu2+ba-Q@mail.gmail.com>
Subject: Re: Pg upgrade from 13.20 to 17.9
To: Balaji Ram <balajiram.ganesan@gmail.com>
Cc: pgsql-admin@lists.postgresql.org
Content-Type: multipart/alternative; boundary="00000000000051ab1e064e3fa120"
Archived-At: 
 <https://www.postgresql.org/message-id/CANzqJaDnQnQnv-Ya2j5xT%2BrxpgsV9%3D7%2BjgGJab%2Beznsu2%2Bba-Q%40mail.gmail.com>
Precedence: bulk

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

On Mon, Mar 30, 2026 at 4:16=E2=80=AFAM 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=E2=80=99t performed a major version upgrade with such a l=
arge
> version gap before, so I=E2=80=99d appreciate any guidance on best practi=
ces,
> 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.

--=20
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

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

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Mar 30, 2026 at 4:16=E2=80=AFAM B=
alaji Ram &lt;<a href=3D"mailto:balajiram.ganesan@gmail.com">balajiram.gane=
san@gmail.com</a>&gt; wrote:</div><div class=3D"gmail_quote gmail_quote_con=
tainer"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto"=
>Hi Everyone,<div dir=3D"auto"></div><div dir=3D"auto"><br></div><div dir=
=3D"auto">I&#39;m planning to upgrade a standalone PostgreSQL cluster from =
**13.20 to 17.9**. I haven=E2=80=99t performed a major version upgrade with=
 such a large version gap before, so I=E2=80=99d appreciate any guidance on=
 best practices, recommended approaches, and things to watch out for.</div>=
</div></blockquote><div><br></div><div>1. Read the PG 14, 15, 16 and 17 rel=
ease notes.</div><div>2. Being on the latest is the latest release (in this=
 case, 13.23) is always Best Practice.</div><div><br></div></div><span clas=
s=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_=
signature"><div dir=3D"ltr">Death to &lt;Redacted&gt;, and butter sauce.<di=
v>Don&#39;t boil me, I&#39;m still alive.<br><div><div>&lt;Redacted&gt; lob=
ster!</div></div></div></div></div></div>

--00000000000051ab1e064e3fa120--