From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Kellerer <shammat@gmx.net>
Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: Re: pg_upgrade(?) not cleaning up old extensions
Date: Sat, 06 Feb 2021 13:47:26 -0500
Message-ID: <248749.1612637246@sss.pgh.pa.us> (raw)
In-Reply-To: <75d85e74-4d01-b3c9-7772-0de1a64a1353@gmx.net>
References: <61ea1e0b-442d-e6c8-1728-916f8376aa11@gmx.net>
<191204.1612631344@sss.pgh.pa.us>
<75d85e74-4d01-b3c9-7772-0de1a64a1353@gmx.net>
Thomas Kellerer <shammat@gmx.net> writes:
> Tom Lane schrieb am 06.02.2021 um 18:09:
>> Yes, that view is supposed to list the versions that are available
>> to be installed.
> So if it is expected to see multiple versions through that view,
> then why do the multiple versions go away when I dump & reload
> the database?
Oh, sorry, -ENOCAFFEINE. I was thinking of
pg_available_extension_versions, which does what I described.
As for pg_available_extensions, that should produce just one row
per extension control file. The only way I can see for it to
produce more is if you have duplicate entries in pg_extension,
which also seems unlikely if not impossible. Maybe you should
provide more detail about exactly what you are seeing, what is
in pg_extension, and what is in your installation's
.../share/extension/ directory.
regards, tom lane
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: tgl@sss.pgh.pa.us, shammat@gmx.net, pgsql-admin@lists.postgresql.org
Subject: Re: pg_upgrade(?) not cleaning up old extensions
In-Reply-To: <248749.1612637246@sss.pgh.pa.us>
* 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