> 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/12/reference/sql-commands/drop-sequence.md). # DROP SEQUENCE DROP SEQUENCE — remove a sequence ## Synopsis ``` DROP SEQUENCE [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ] ``` ## Description `DROP SEQUENCE` removes sequence number generators. A sequence can only be dropped by its owner or a superuser. ## Parameters `IF EXISTS` Do not throw an error if the sequence does not exist. A notice is issued in this case. *`name`* The name (optionally schema-qualified) of a sequence. `CASCADE` Automatically drop objects that depend on the sequence, and in turn all objects that depend on those objects (see [Section 5.13](https://www.postgresql.org/docs/10/static/ddl-depend.html)). `RESTRICT` Refuse to drop the sequence if any objects depend on it. This is the default. ## Examples To remove the sequence `serial`: ``` DROP SEQUENCE serial; ``` ## Compatibility `DROP SEQUENCE` conforms to the SQL standard, except that the standard only allows one sequence to be dropped per command, and apart from the `IF EXISTS` option, which is a PostgreSQL extension. ## See Also [CREATE SEQUENCE](/12/reference/sql-commands/create-sequence.md), [ALTER SEQUENCE](/12/reference/sql-commands/alter-sequence.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/12/reference/sql-commands/drop-sequence.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.