| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Kellerer <shammat(at)gmx(dot)net> |
| Cc: | "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_upgrade(?) not cleaning up old extensions |
| Date: | 2021-02-06 18:47:26 |
| Message-ID: | 248749.1612637246@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Thomas Kellerer <shammat(at)gmx(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2021-02-07 16:06:22 | Re: pg_upgrade(?) not cleaning up old extensions |
| Previous Message | Jeff Janes | 2021-02-06 18:42:11 | Re: pg_upgrade(?) not cleaning up old extensions |