public inbox for [email protected]
help / color / mirror / Atom feedFrom: Alvaro Herrera <[email protected]>
To: plsqlvids01 plsqlvids01 <[email protected]>
Cc: [email protected]
Subject: Re: unable to upgrade postgres extensions
Date: Wed, 21 Aug 2024 18:09:26 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAFsfSru+ZfPVF8xQiPf2Ug4YBS6fSzBC+TCos_3ey7EamnFpsg@mail.gmail.com>
On 2024-Aug-21, plsqlvids01 plsqlvids01 wrote:
> 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?
> postgres=> select * from pg_available_extensions where name in
> ('pgaudit','pg_cron');
> name | default_version | installed_version |
> comment---------+-----------------+-------------------+---------------------------------
> pgaudit | 16.0 | 1.4.3 | provides auditing functionality
> pg_cron | 1.6 | 1.6 | Job scheduler for PostgreSQL
>
> postgres=> ALTER EXTENSION pgaudit update to "16.0";
> ERROR: extension "pgaudit" has no update path from version "1.4.3" to
> version "16.0"
That sounds like an RDS problem, so you should be talking to Amazon
support. But maybe see in "select * from
pg_available_extension_versions" if the versions their docco claims are
available, actually are. Also, the fact that a version is available
does not automatically mean that an upgrade path exists; you may need to
do the upgrade in multiple jumps, for instance for pgAudit go from 1.4.3
to 1.6.2 first, then to 1.7.0 finally to 16.0.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"How strange it is to find the words "Perl" and "saner" in such close
proximity, with no apparent sense of irony. I doubt that Larry himself
could have managed it." (ncm, http://lwn.net/Articles/174769/)
view thread (4+ messages) latest in thread
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