Rajkumar Raghuwanshi <rajkumar.raghuwan...@enterprisedb.com> writes: > I have observed that even after dropping operator class, not able to drop > schema containing it. below is a example.
You didn't read the error message closely: > *postgres=# DROP SCHEMA sch_test;ERROR: cannot drop schema sch_test > because other objects depend on itDETAIL: operator family > sch_test.custom_opclass_test for access method hash depends on schema > sch_testHINT: Use DROP ... CASCADE to drop the dependent objects too.* The operator class is gone, but the operator family that contained it still exists. CREATE OPERATOR CLASS will create a containing family if you don't specify one, but DROP OPERATOR CLASS won't automatically remove such a family. (If it did, it might destroy other operator classes that had been added to that family later.) Probably the easiest answer is to use DROP OPERATOR FAMILY instead. regards, tom lane -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers