> 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/16/reference/sql-commands/drop-publication.md). # DROP PUBLICATION DROP PUBLICATION — remove a publication ### Synopsis ``` DROP PUBLICATION [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ] ``` ### Description `DROP PUBLICATION` removes an existing publication from the database. A publication can only be dropped by its owner or a superuser. ### Parameters `IF EXISTS` Do not throw an error if the publication does not exist. A notice is issued in this case. *`name`* The name of an existing publication. `CASCADE`\ `RESTRICT` These key words do not have any effect, since there are no dependencies on publications. ### Examples Drop a publication: ``` DROP PUBLICATION mypublication; ``` ### Compatibility `DROP PUBLICATION` is a PostgreSQL extension. ### See Also [CREATE PUBLICATION](/16/reference/sql-commands/create-publication.md), [ALTER PUBLICATION](/16/reference/sql-commands/alter-publication.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/16/reference/sql-commands/drop-publication.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.