> 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/13/client-interfaces/the-information-schema/parameters.md).

# 36.33. parameters

The view `parameters` contains information about the parameters (arguments) of all functions in the current database. Only those functions are shown that the current user has access to (by way of being the owner or having some privilege).

#### **Table 36.31. `parameters` Columns**

| <p>Column Type</p><p>Description</p>                                                                                                                                                                                                                                                                                                                                                               |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <p><code>specific\_catalog</code> <code>sql\_identifier</code></p><p>Name of the database containing the function (always the current database)</p>                                                                                                                                                                                                                                                |
| <p><code>specific\_schema</code> <code>sql\_identifier</code></p><p>Name of the schema containing the function</p>                                                                                                                                                                                                                                                                                 |
| <p><code>specific\_name</code> <code>sql\_identifier</code></p><p>The “specific name” of the function. See <a href="https://www.postgresql.org/docs/13/infoschema-routines.html">Section 36.41</a> for more information.</p>                                                                                                                                                                       |
| <p><code>ordinal\_position</code> <code>cardinal\_number</code></p><p>Ordinal position of the parameter in the argument list of the function (count starts at 1)</p>                                                                                                                                                                                                                               |
| <p><code>parameter\_mode</code> <code>character\_data</code></p><p><code>IN</code> for input parameter, <code>OUT</code> for output parameter, and <code>INOUT</code> for input/output parameter.</p>                                                                                                                                                                                              |
| <p><code>is\_result</code> <code>yes\_or\_no</code></p><p>Applies to a feature not available in PostgreSQL</p>                                                                                                                                                                                                                                                                                     |
| <p><code>as\_locator</code> <code>yes\_or\_no</code></p><p>Applies to a feature not available in PostgreSQL</p>                                                                                                                                                                                                                                                                                    |
| <p><code>parameter\_name</code> <code>sql\_identifier</code></p><p>Name of the parameter, or null if the parameter has no name</p>                                                                                                                                                                                                                                                                 |
| <p><code>data\_type</code> <code>character\_data</code></p><p>Data type of the parameter, if it is a built-in type, or <code>ARRAY</code> if it is some array (in that case, see the view <code>element\_types</code>), else <code>USER-DEFINED</code> (in that case, the type is identified in <code>udt\_name</code> and associated columns).</p>                                                |
| <p><code>character\_maximum\_length</code> <code>cardinal\_number</code></p><p>Always null, since this information is not applied to parameter data types in PostgreSQL</p>                                                                                                                                                                                                                        |
| <p><code>character\_octet\_length</code> <code>cardinal\_number</code></p><p>Always null, since this information is not applied to parameter data types in PostgreSQL</p>                                                                                                                                                                                                                          |
| <p><code>character\_set\_catalog</code> <code>sql\_identifier</code></p><p>Applies to a feature not available in PostgreSQL</p>                                                                                                                                                                                                                                                                    |
| <p><code>character\_set\_schema</code> <code>sql\_identifier</code></p><p>Applies to a feature not available in PostgreSQL</p>                                                                                                                                                                                                                                                                     |
| <p><code>character\_set\_name</code> <code>sql\_identifier</code></p><p>Applies to a feature not available in PostgreSQL</p>                                                                                                                                                                                                                                                                       |
| <p><code>collation\_catalog</code> <code>sql\_identifier</code></p><p>Always null, since this information is not applied to parameter data types in PostgreSQL</p>                                                                                                                                                                                                                                 |
| <p><code>collation\_schema</code> <code>sql\_identifier</code></p><p>Always null, since this information is not applied to parameter data types in PostgreSQL</p>                                                                                                                                                                                                                                  |
| <p><code>collation\_name</code> <code>sql\_identifier</code></p><p>Always null, since this information is not applied to parameter data types in PostgreSQL</p>                                                                                                                                                                                                                                    |
| <p><code>numeric\_precision</code> <code>cardinal\_number</code></p><p>Always null, since this information is not applied to parameter data types in PostgreSQL</p>                                                                                                                                                                                                                                |
| <p><code>numeric\_precision\_radix</code> <code>cardinal\_number</code></p><p>Always null, since this information is not applied to parameter data types in PostgreSQL</p>                                                                                                                                                                                                                         |
| <p><code>numeric\_scale</code> <code>cardinal\_number</code></p><p>Always null, since this information is not applied to parameter data types in PostgreSQL</p>                                                                                                                                                                                                                                    |
| <p><code>datetime\_precision</code> <code>cardinal\_number</code></p><p>Always null, since this information is not applied to parameter data types in PostgreSQL</p>                                                                                                                                                                                                                               |
| <p><code>interval\_type</code> <code>character\_data</code></p><p>Always null, since this information is not applied to parameter data types in PostgreSQL</p>                                                                                                                                                                                                                                     |
| <p><code>interval\_precision</code> <code>cardinal\_number</code></p><p>Always null, since this information is not applied to parameter data types in PostgreSQL</p>                                                                                                                                                                                                                               |
| <p><code>udt\_catalog</code> <code>sql\_identifier</code></p><p>Name of the database that the data type of the parameter is defined in (always the current database)</p>                                                                                                                                                                                                                           |
| <p><code>udt\_schema</code> <code>sql\_identifier</code></p><p>Name of the schema that the data type of the parameter is defined in</p>                                                                                                                                                                                                                                                            |
| <p><code>udt\_name</code> <code>sql\_identifier</code></p><p>Name of the data type of the parameter</p>                                                                                                                                                                                                                                                                                            |
| <p><code>scope\_catalog</code> <code>sql\_identifier</code></p><p>Applies to a feature not available in PostgreSQL</p>                                                                                                                                                                                                                                                                             |
| <p><code>scope\_schema</code> <code>sql\_identifier</code></p><p>Applies to a feature not available in PostgreSQL</p>                                                                                                                                                                                                                                                                              |
| <p><code>scope\_name</code> <code>sql\_identifier</code></p><p>Applies to a feature not available in PostgreSQL</p>                                                                                                                                                                                                                                                                                |
| <p><code>maximum\_cardinality</code> <code>cardinal\_number</code></p><p>Always null, because arrays always have unlimited maximum cardinality in PostgreSQL</p>                                                                                                                                                                                                                                   |
| <p><code>dtd\_identifier</code> <code>sql\_identifier</code></p><p>An identifier of the data type descriptor of the parameter, unique among the data type descriptors pertaining to the function. This is mainly useful for joining with other instances of such identifiers. (The specific format of the identifier is not defined and not guaranteed to remain the same in future versions.)</p> |
| <p><code>parameter\_default</code> <code>character\_data</code></p><p>The default expression of the parameter, or null if none or if the function is not owned by a currently enabled role.</p>                                                                                                                                                                                                    |


---

# 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/13/client-interfaces/the-information-schema/parameters.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.