public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: pgsql-general <[email protected]>
Subject: Re: Guidance on PgSql Upgrade from 17.3 to 18.2
Date: Wed, 11 Mar 2026 09:04:17 -0400
Message-ID: <CANzqJaD5gVfm4QHEdYiqtSva4KRq++GLJf1vjqOgGyiOzL4ZpA@mail.gmail.com> (raw)
In-Reply-To: <CAObRBE0Ohhpo_VqFgA4n9os1Tg_SinDuxgK0meV+XBScWpyrSQ@mail.gmail.com>
References: <CAObRBE0Ohhpo_VqFgA4n9os1Tg_SinDuxgK0meV+XBScWpyrSQ@mail.gmail.com>
On Wed, Mar 11, 2026 at 9:00 AM Pratibha Shende <[email protected]>
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.
--
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: [email protected]
Cc: [email protected]
Subject: Re: Guidance on PgSql Upgrade from 17.3 to 18.2
In-Reply-To: <CANzqJaD5gVfm4QHEdYiqtSva4KRq++GLJf1vjqOgGyiOzL4ZpA@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