> 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/internals/54.-system-views/pg_cursors.md).

# 54.6. pg\_cursors

## 54.6. pg\_cursors

The `pg_cursors` view lists the cursors that are currently available. Cursors can be defined in several ways:

* via the [`DECLARE`](/15/reference/sql-commands/declare.md) statement in SQL
* via the Bind message in the frontend/backend protocol, as described in [Section 55.2.3](/15/internals/52.-frontend-backend-protocol/52.2.-message-flow.md#PROTOCOL-FLOW-EXT-QUERY)
* via the Server Programming Interface (SPI), as described in [Section 47.1](/15/server-programming/server-programming-interface/spi-interface.md)

The `pg_cursors` view displays cursors created by any of these means. Cursors only exist for the duration of the transaction that defines them, unless they have been declared `WITH HOLD`. Therefore non-holdable cursors are only present in the view until the end of their creating transaction.

### Note

Cursors are used internally to implement some of the components of PostgreSQL, such as procedural languages. Therefore, the `pg_cursors` view might include cursors that have not been explicitly created by the user.

**Table 54.6. `pg_cursors` Columns**

| <p>Column Type</p><p>Description</p>                                                                                                                                                                                          |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <p><code>name</code> <code>text</code></p><p>The name of the cursor</p>                                                                                                                                                       |
| <p><code>statement</code> <code>text</code></p><p>The verbatim query string submitted to declare this cursor</p>                                                                                                              |
| <p><code>is\_holdable</code> <code>bool</code></p><p><code>true</code> if the cursor is holdable (that is, it can be accessed after the transaction that declared the cursor has committed); <code>false</code> otherwise</p> |
| <p><code>is\_binary</code> <code>bool</code></p><p><code>true</code> if the cursor was declared <code>BINARY</code>; <code>false</code> otherwise</p>                                                                         |
| <p><code>is\_scrollable</code> <code>bool</code></p><p><code>true</code> if the cursor is scrollable (that is, it allows rows to be retrieved in a nonsequential manner); <code>false</code> otherwise</p>                    |
| <p><code>creation\_time</code> <code>timestamptz</code></p><p>The time at which the cursor was declared</p>                                                                                                                   |

The `pg_cursors` view is read-only.

***

原文：[PostgreSQL 15.19 Documentation](/15/internals/54.-system-views/pg_cursors.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/internals/54.-system-views/pg_cursors.md?ask=<question>&goal=<user_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.