From: Tom Lane <tgl@sss.pgh.pa.us>
To: charles@twenty.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18367: Cannot drop schema
In-reply-to: <18367-8d35c5ecb617d821@postgresql.org>
References: <18367-8d35c5ecb617d821@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Tue, 27 Feb 2024 16:11:29 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2135023.1709057683.1@sss.pgh.pa.us>
Date: Tue, 27 Feb 2024 13:14:43 -0500
Message-ID: <2135024.1709057683@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2135024.1709057683%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> When trying to drop a schema using DROP SCHEMA "brokenSchema"; 

> I'm facing the following error:
> requested object address for unsupported object class 2: text result ""

> The schema is empty from any table, type, trigger...

That shouldn't happen :-(.  I am guessing the cause is a corrupt
entry in pg_depend.  Class 2 is OCLASS_TYPE, so apparently some
type got dropped but its pg_depend entry wasn't cleaned out, so
DROP SCHEMA thinks there's still a dependent object.

I would try to pg_dump the database, and if you can do that and
reload successfully then discard the original.  If you've found
one bit of catalog corruption there's likely more.

			regards, tom lane