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

# 37.41. routine\_privileges

The view `routine_privileges` identifies all privileges granted on functions to a currently enabled role or by a currently enabled role. There is one row for each combination of function, grantor, and grantee.

#### **Table 37.39. `routine_privileges` Columns**

| <p>Column Type</p><p>Description</p>                                                                                                                                                                                              |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <p><code>grantor</code> <code>sql\_identifier</code></p><p>Name of the role that granted the privilege</p>                                                                                                                        |
| <p><code>grantee</code> <code>sql\_identifier</code></p><p>Name of the role that the privilege was granted to</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/current/infoschema-routines.html">Section 37.45</a> for more information.</p> |
| <p><code>routine\_catalog</code> <code>sql\_identifier</code></p><p>Name of the database containing the function (always the current database)</p>                                                                                |
| <p><code>routine\_schema</code> <code>sql\_identifier</code></p><p>Name of the schema containing the function</p>                                                                                                                 |
| <p><code>routine\_name</code> <code>sql\_identifier</code></p><p>Name of the function (might be duplicated in case of overloading)</p>                                                                                            |
| <p><code>privilege\_type</code> <code>character\_data</code></p><p>Always <code>EXECUTE</code> (the only privilege type for functions)</p>                                                                                        |
| <p><code>is\_grantable</code> <code>yes\_or\_no</code></p><p><code>YES</code> if the privilege is grantable, <code>NO</code> if not</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 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/client-interfaces/the-information-schema/routine_privileges.md?ask=<question>&goal=<endgoal>
```

`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.