> 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/client-interfaces/the-information-schema/36.42.-sequences.md).
# 37.47. sequences
The view `sequences` contains all sequences defined in the current database. Only those sequences are shown that the current user has access to (by way of being the owner or having some privilege).
#### **Table 37.45. `sequences` Columns**
| Column Type
Description
|
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| sequence\_catalog sql\_identifier
Name of the database that contains the sequence (always the current database)
|
| sequence\_schema sql\_identifier
Name of the schema that contains the sequence
|
| sequence\_name sql\_identifier
Name of the sequence
|
| data\_type character\_data
The data type of the sequence.
|
| numeric\_precision cardinal\_number
This column contains the (declared or implicit) precision of the sequence data type (see above). The precision indicates the number of significant digits. It can be expressed in decimal (base 10) or binary (base 2) terms, as specified in the column numeric\_precision\_radix.
|
| numeric\_precision\_radix cardinal\_number
This column indicates in which base the values in the columns numeric\_precision and numeric\_scale are expressed. The value is either 2 or 10.
|
| numeric\_scale cardinal\_number
This column contains the (declared or implicit) scale of the sequence data type (see above). The scale indicates the number of significant digits to the right of the decimal point. It can be expressed in decimal (base 10) or binary (base 2) terms, as specified in the column numeric\_precision\_radix.
|
| start\_value character\_data
The start value of the sequence
|
| minimum\_value character\_data
The minimum value of the sequence
|
| maximum\_value character\_data
The maximum value of the sequence
|
| increment character\_data
The increment of the sequence
|
| cycle\_option yes\_or\_no
YES if the sequence cycles, else NO
|
Note that in accordance with the SQL standard, the start, minimum, maximum, and increment values are returned as character strings.
---
# 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/client-interfaces/the-information-schema/36.42.-sequences.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.