Re: NEEDING HELP: dropping none-existing extension - Mailing list pgsql-admin

From Axel Rau
Subject Re: NEEDING HELP: dropping none-existing extension
Date
Msg-id 189CA253-CD42-4B75-8883-624690E1DA1A@Chaos1.DE
Whole thread Raw
In response to Re: NEEDING HELP: dropping none-existing extension  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin


Am 04.04.2020 um 18:09 schrieb Tom Lane <tgl@sss.pgh.pa.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

Attachment

pgsql-admin by date:

Previous
From: Ron
Date:
Subject: Re: NEEDING HELP: dropping none-existing extension
Next
From: Saad SENOUCI
Date:
Subject: Problem with pgadmin4 : displaying data in the query editor