> 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/close.md). # CLOSE ## CLOSE CLOSE — close a cursor ### Synopsis ``` CLOSE { name | ALL } ``` ### Description `CLOSE` frees the resources associated with an open cursor. After the cursor is closed, no subsequent operations are allowed on it. A cursor should be closed when it is no longer needed. Every non-holdable open cursor is implicitly closed when a transaction is terminated by `COMMIT` or `ROLLBACK`. A holdable cursor is implicitly closed if the transaction that created it aborts via `ROLLBACK`. If the creating transaction successfully commits, the holdable cursor remains open until an explicit `CLOSE` is executed, or the client disconnects. ### Parameters *`name`* The name of an open cursor to close. `ALL` Close all open cursors. ### Notes PostgreSQL does not have an explicit `OPEN` cursor statement; a cursor is considered open when it is declared. Use the [`DECLARE`](/15/reference/sql-commands/declare.md) statement to declare a cursor. You can see all available cursors by querying the [`pg_cursors`](/15/internals/54.-system-views/pg_cursors.md) system view. If a cursor is closed after a savepoint which is later rolled back, the `CLOSE` is not rolled back; that is, the cursor remains closed. ### Examples Close the cursor `liahona`: ``` CLOSE liahona; ``` ### Compatibility `CLOSE` is fully conforming with the SQL standard. `CLOSE ALL` is a PostgreSQL extension. ### See Also [DECLARE](/15/reference/sql-commands/declare.md), [FETCH](/15/reference/sql-commands/fetch.md), [MOVE](/15/reference/sql-commands/move.md) *** 原文：[PostgreSQL 15.19 Documentation](/15/reference/sql-commands/close.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/close.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.