> For the complete documentation index, see [llms.txt](https://docs.postgresql.tw/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.postgresql.tw/15/reference/sql-commands/drop-access-method.md). # DROP ACCESS METHOD DROP ACCESS METHOD — remove an access method ### Synopsis ``` DROP ACCESS METHOD [ IF EXISTS ] name [ CASCADE | RESTRICT ] ``` ### Description `DROP ACCESS METHOD` removes an existing access method. Only superusers can drop access methods. ### Parameters `IF EXISTS` Do not throw an error if the access method does not exist. A notice is issued in this case. *`name`* The name of an existing access method. `CASCADE` Automatically drop objects that depend on the access method (such as operator classes, operator families, and indexes), and in turn all objects that depend on those objects (see [Section 5.14](/15/the-sql-language/ddl/dependency-tracking.md)). `RESTRICT` Refuse to drop the access method if any objects depend on it. This is the default. ### Examples Drop the access method `heptree`: ``` DROP ACCESS METHOD heptree; ``` ### Compatibility `DROP ACCESS METHOD` is a PostgreSQL extension. ### See Also [CREATE ACCESS METHOD](/15/reference/sql-commands/create-access-method.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.postgresql.tw/15/reference/sql-commands/drop-access-method.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.