public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: plsqlvids01 plsqlvids01 <[email protected]>
Cc: [email protected]
Subject: Re: unable to upgrade postgres extensions
Date: Wed, 21 Aug 2024 18:36:40 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAFsfSru+ZfPVF8xQiPf2Ug4YBS6fSzBC+TCos_3ey7EamnFpsg@mail.gmail.com>
References: <CAFsfSru+ZfPVF8xQiPf2Ug4YBS6fSzBC+TCos_3ey7EamnFpsg@mail.gmail.com>

plsqlvids01 plsqlvids01 <[email protected]> writes:
> AWS RDS Postgres database on v12.17 is upgraded to v16.1, as per
> https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-extensions.html#postg...
> am
> trying to upgrade pg_cron and pgaudit extensions but it keeps throwing the
> 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

view thread (4+ messages)

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], [email protected], [email protected]
  Subject: Re: unable to upgrade postgres extensions
  In-Reply-To: <[email protected]>

* 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