Thread: NEEDING HELP: dropping none-existing extension
Hi all during upgrade from 11 to 12, pg_upgrade errors out: - - - could not load library "$libdir/pg_repack": ERROR: could not access file "$libdir/pg_repack": No such file or directory Database: development Database: operations Database: pki_op - - - I find no extension pg_repack, only views with that name in those DBs. While trying to drop them, I get: - - - ERROR: cannot drop schema repack because extension pg_repack requires it HINT: You can drop extension pg_repack instead. - - - How can I get rid of those views? Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius
Attachment
Axel Rau <Axel.Rau@chaos1.de> writes: > during upgrade from 11 to 12, pg_upgrade errors out: > - - - > could not load library "$libdir/pg_repack": ERROR: could not access file "$libdir/pg_repack": No such file or directory > Database: development > Database: operations > Database: pki_op > - - - > I find no extension pg_repack, only views with that name in those DBs. > While trying to drop them, I get: > - - - > ERROR: cannot drop schema repack because extension pg_repack requires it HINT: You can drop extension pg_repack instead. 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 ... regards, tom lane
On 4/4/20 10:48 AM, Axel Rau wrote: > Hi all > > during upgrade from 11 to 12, pg_upgrade errors out: > - - - > could not load library "$libdir/pg_repack": ERROR: could not access file "$libdir/pg_repack": No such file or directory > Database: development > Database: operations > Database: pki_op > - - - > I find no extension pg_repack, only views with that name in those DBs. > While trying to drop them, I get: > - - - > ERROR: cannot drop schema repack because extension pg_repack requires it HINT: You can drop extension pg_repack instead. > - - - > > How can I get rid of those views? Are you trying to drop the extension pg_repack *before* doing the upgrade? -- Angular momentum makes the world go 'round.
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 ...
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
PGP-Key: CDE74120 ☀ computing @ chaos claudius