From: Tom Lane <tgl@sss.pgh.pa.us>
To: plsqlvids01 plsqlvids01 <plsqlvids01@gmail.com>
cc: pgsql-general@lists.postgresql.org
Subject: Re: unable to upgrade postgres extensions
In-reply-to: <CAFsfSru+ZfPVF8xQiPf2Ug4YBS6fSzBC+TCos_3ey7EamnFpsg@mail.gmail.com>
References: <CAFsfSru+ZfPVF8xQiPf2Ug4YBS6fSzBC+TCos_3ey7EamnFpsg@mail.gmail.com>
Comments: In-reply-to plsqlvids01 plsqlvids01 <plsqlvids01@gmail.com>
	message dated "Wed, 21 Aug 2024 15:14:00 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1896126.1724279800.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 21 Aug 2024 18:36:40 -0400
Message-ID: <1896127.1724279800@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/1896127.1724279800%40sss.pgh.pa.us>
Precedence: bulk

plsqlvids01 plsqlvids01 <plsqlvids01@gmail.com> writes:
> AWS RDS Postgres database on v12.17 is upgraded to v16.1, as per
> https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/post=
gresql-extensions.html#postgresql-extensions-16x
> am
> trying to upgrade pg_cron and pgaudit extensions but it keeps throwing t=
he
> same error, how to upgrade them?

You seem to be assuming that PG extensions have versioning matching
the core server.  There's no requirement for that, and it doesn't
look like these extensions attempt to keep those numbers in sync.

The underlying compiled modules (.so files) do need to be updated
for each major server version.  But if they load and work then
that's happened.  The "extension version" is just an arbitrary
identifier for the version of the extension's SQL-level declarations,
which frequently don't need to change for a server update.

			regards, tom lane