MIME-Version: 1.0
References: <CAObRBE0Ohhpo_VqFgA4n9os1Tg_SinDuxgK0meV+XBScWpyrSQ@mail.gmail.com>
In-Reply-To: <CAObRBE0Ohhpo_VqFgA4n9os1Tg_SinDuxgK0meV+XBScWpyrSQ@mail.gmail.com>
From: Ron Johnson <ronljohnsonjr@gmail.com>
Date: Wed, 11 Mar 2026 09:04:17 -0400
Message-ID: <CANzqJaD5gVfm4QHEdYiqtSva4KRq++GLJf1vjqOgGyiOzL4ZpA@mail.gmail.com>
Subject: Re: Guidance on PgSql Upgrade from 17.3 to 18.2
To: pgsql-general <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000a90aae064cbf4633"
Archived-At: <https://www.postgresql.org/message-id/CANzqJaD5gVfm4QHEdYiqtSva4KRq%2B%2BGLJf1vjqOgGyiOzL4ZpA%40mail.gmail.com>
Precedence: bulk

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

On Wed, Mar 11, 2026 at 9:00=E2=80=AFAM Pratibha Shende <shende.pratibha@gm=
ail.com>
wrote:

>
> Hello Team,
>
> I am planning to upgrade PostgreSQL from 17.3 to 18.2 and would like your
> guidance on the key considerations before proceeding.
>
> Could you please advise on:
>
> 1.Important points to consider during the upgrade.
> 2. Features deprecated or removed between these versions.
>
> Any best practices or compatibility recommendations would be appreciated.
>

1. Read the release notes. https://www.postgresql.org/docs/release/18.0/
2. Update the existing instance to 17.9 beforehand.

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

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

<div dir=3D"ltr"><div dir=3D"ltr">On Wed, Mar 11, 2026 at 9:00=E2=80=AFAM P=
ratibha Shende &lt;<a href=3D"mailto:shende.pratibha@gmail.com">shende.prat=
ibha@gmail.com</a>&gt; wrote:</div><div class=3D"gmail_quote gmail_quote_co=
ntainer"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto=
"><div dir=3D"auto"><div><div dir=3D"auto"><br></div><div dir=3D"auto">Hell=
o Team,</div><div dir=3D"auto"><br></div><div dir=3D"auto">I am planning to=
 upgrade PostgreSQL from 17.3 to 18.2 and would like your guidance on the k=
ey considerations before proceeding.</div><div dir=3D"auto"><br></div><div =
dir=3D"auto">Could you please advise on:</div><div dir=3D"auto"><br></div><=
div dir=3D"auto">1.Important points to consider during the upgrade.</div><d=
iv dir=3D"auto">2. Features deprecated or removed between these versions.</=
div><div dir=3D"auto"><br></div><div dir=3D"auto">Any best practices or com=
patibility recommendations would be appreciated.</div></div></div></div></b=
lockquote><div></div></div><div><br></div><div>1. Read the release notes. <=
a href=3D"https://www.postgresql.org/docs/release/18.0/">https://www.postgr=
esql.org/docs/release/18.0/</a></div><div>2. Update the existing instance t=
o 17.9 beforehand.</div><div><br></div><span class=3D"gmail_signature_prefi=
x">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr=
">Death to &lt;Redacted&gt;, and butter sauce.<div>Don&#39;t boil me, I&#39=
;m still alive.<br><div><div>&lt;Redacted&gt; lobster!</div></div></div></d=
iv></div></div>

--000000000000a90aae064cbf4633--