> 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/reference/sql-commands/sql-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`](/reference/sql-commands/sql-declare.md) statement to declare a cursor. You can see all available cursors by querying the [`pg_cursors`](/internals/views/view-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](/reference/sql-commands/sql-declare.md), [FETCH](/reference/sql-commands/sql-fetch.md), [MOVE](/reference/sql-commands/sql-move.md) *** 原文：[PostgreSQL 18.6 Documentation](https://www.postgresql.org/docs/18/sql-close.html)（英文原文，待翻譯） --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.postgresql.tw/reference/sql-commands/sql-close.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.