From: Thomas Kellerer <shammat@gmx.net>
To: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Cc: Jeff Janes <jeff.janes@gmail.com>
Subject: Re: pg_upgrade(?) not cleaning up old extensions
Date: Sun, 7 Feb 2021 17:06:22 +0100
Message-ID: <4262c6e7-e8fd-d1d9-fc1f-a419403a4cb4@gmx.net> (raw)
In-Reply-To: <CAMkU=1wk=HtV1-rbrNyDbhsyNGeDDiu8OUpmE7skeW6CAn_FGw@mail.gmail.com>
References: <61ea1e0b-442d-e6c8-1728-916f8376aa11@gmx.net>
<CAMkU=1wk=HtV1-rbrNyDbhsyNGeDDiu8OUpmE7skeW6CAn_FGw@mail.gmail.com>
Jeff Janes schrieb am 06.02.2021 um 19:42:
> On Sat, Feb 6, 2021 at 7:24 AM Thomas Kellerer <shammat@gmx.net <mailto:shammat@gmx.net>> wrote:
>
> Hello,
>
> I have a (test) database that has been upgraded several times from 9.4 to 13 using pg_upgrade.
>
> I have noticed that when I look at pg_available_extensions many extensions are listed with multiple versions even though only the latest one is actually used.
>
>
> I can't reproduce this. Are you sure you aren't looking at pg_available_extension_versions ? Could you show some example output?
Hmm, I could have sworn I was looking at pg_available_extensions - but maybe I wasn't.
But as I can't reproduce this after a dump & reload and it's really not a big deal,
let's just assume I was indeed using the wrong view.
Thomas
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: pgsql-admin@postgresql.org
Cc: shammat@gmx.net, pgsql-admin@lists.postgresql.org, jeff.janes@gmail.com
Subject: Re: pg_upgrade(?) not cleaning up old extensions
In-Reply-To: <4262c6e7-e8fd-d1d9-fc1f-a419403a4cb4@gmx.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox