From: Tom Lane <tgl@sss.pgh.pa.us>
To: Matt Gibbins <matt_gibbins@fastmail.com.au>
cc: pgsql-admin@lists.postgresql.org
Subject: Re: Unable to drop extension dblink
In-reply-to: <07dbf1c4-4871-4348-b41a-d0a800da7465@fastmail.com.au>
References: <07dbf1c4-4871-4348-b41a-d0a800da7465@fastmail.com.au>
Comments: In-reply-to Matt Gibbins <matt_gibbins@fastmail.com.au>
	message dated "Tue, 19 Sep 2023 08:04:33 +1000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <263516.1695086165.1@sss.pgh.pa.us>
Date: Mon, 18 Sep 2023 21:16:05 -0400
Message-ID: <263517.1695086165@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/263517.1695086165%40sss.pgh.pa.us>
Precedence: bulk

Matt Gibbins <matt_gibbins@fastmail.com.au> writes:
> In the process of removing extensions not required on the database I was 
> in the process of removing the dblink extension from the postgres database.
> First attempt to drop the extension failed with 'ERROR: schema 
> "ag_catalog" does not exist'.

Something is very broken there.  I wonder if this error could be a
corrupted reference to "pg_catalog" --- but I don't really see what
the details could be, because we don't store schema references as
textual names, rather OIDs.  Your follow-on errors also look more
like catalog corruption than anything sane.  With only these limited
factoids to look at, it's impossible to say just what's going on
--- but creating bogus objects in response to these errors is
unlikely to get you anywhere.  What PG version is this, what's
the installation's history, have you suffered any catastrophic
failures in the recent past?

			regards, tom lane