From: Tom Lane <tgl@sss.pgh.pa.us>
To: Axel Rau <Axel.Rau@chaos1.de>
cc: pgsql-admin@lists.postgresql.org
Subject: Re: NEEDING HELP: dropping none-existing extension
In-reply-to: <4A197984-1E5A-410C-ACDF-83E18A4734E5@Chaos1.DE>
References: <4A197984-1E5A-410C-ACDF-83E18A4734E5@Chaos1.DE>
Comments: In-reply-to Axel Rau <Axel.Rau@chaos1.de>
	message dated "Sat, 04 Apr 2020 17:48:24 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <25614.1586016574.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sat, 04 Apr 2020 12:09:34 -0400
Message-ID: <25615.1586016574@sss.pgh.pa.us>
Precedence: bulk

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 fil=
e "$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 =3D 'pg_repack', or
the message text could not have been generated.  So look again ...

			regards, tom lane