Subject: Re: pg_upgrade(?) not cleaning up old extensions
To: "pgsql-admin@lists.postgresql.org" <pgsql-admin@lists.postgresql.org>
Cc: Jeff Janes <jeff.janes@gmail.com>
References: <61ea1e0b-442d-e6c8-1728-916f8376aa11@gmx.net>
 <CAMkU=1wk=HtV1-rbrNyDbhsyNGeDDiu8OUpmE7skeW6CAn_FGw@mail.gmail.com>
From: Thomas Kellerer <shammat@gmx.net>
Message-ID: <4262c6e7-e8fd-d1d9-fc1f-a419403a4cb4@gmx.net>
Date: Sun, 7 Feb 2021 17:06:22 +0100
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.21)
 Gecko/20090302 Thunderbird/2.0.0.21 Mnenhy/0.7.5.666
MIME-Version: 1.0
In-Reply-To: 
 <CAMkU=1wk=HtV1-rbrNyDbhsyNGeDDiu8OUpmE7skeW6CAn_FGw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: de-DE
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

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 exte=
nsions are listed with multiple versions even though only the latest one i=
s actually used.
>
>
> I can't reproduce this.=C2=A0 Are you sure you aren't looking at=C2=A0pg=
_available_extension_versions ?=C2=A0 Could you show some example output?


Hmm, I could have sworn I was looking at pg_available_extensions - but may=
be 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