Re: NEEDING HELP: dropping none-existing extension

From: Axel Rau <Axel(dot)Rau(at)chaos1(dot)de>
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: NEEDING HELP: dropping none-existing extension
Date: 2020-04-04 16:47:49
Message-ID: 189CA253-CD42-4B75-8883-624690E1DA1A@Chaos1.DE
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

> Am 04.04.2020 um 18:09 schrieb Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>
> It is really, really, really difficult to believe that you got that
> error if there's not any extension pg_repack in the database. Even
> granting the possibility of catalog corruption, there would have
> to be some row in pg_extension containing extname = 'pg_repack', or
> the message text could not have been generated. So look again ...

You are right:
operations=# select * from pg_extension;
extname | extowner | extnamespace | extrelocatable | extversion | extconfig | extcondition
-----------+----------+--------------+----------------+------------+-----------+--------------
plpgsql | 10 | 11 | f | 1.0 | |
adminpack | 10 | 11 | f | 1.0 | |
pg_repack | 16386 | 2200 | f | 1.4.5 | |
(3 rows)
I was misleaded by pgadmin4 in the 1st place.
psql
drop extension pg_repack cascade ;
did the job. (-:

Thanks a lot, Axel
---
PGP-Key: CDE74120 ☀ computing @ chaos claudius

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Saad SENOUCI 2020-04-05 15:21:55 Problem with pgadmin4 : displaying data in the query editor
Previous Message Ron 2020-04-04 16:24:02 Re: NEEDING HELP: dropping none-existing extension