PostgreSQL
36.40. routines
The view routines
contains 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.38. routines
Columns
Name | Data Type | Description |
---|---|---|
|
|
Name of the database containing the function (always the current database) |
|
|
Name of the schema containing the function |
|
|
The “[.quote]#specific name”# of the function. This is a name that uniquely identifies the function in the schema, even if the real name of the function is overloaded. The format of the specific name is not defined, it should only be used to compare it to other instances of specific routine names. |
|
|
Name of the database containing the function (always the current database) |
|
|
Name of the schema containing the function |
|
|
Name of the function (might be duplicated in case of overloading) |
|
|
Always |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Return data type of the function, if it is a built-in type, or |
|
|
Always null, since this information is not applied to return data types in PostgreSQL |
|
|
Always null, since this information is not applied to return data types in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Always null, since this information is not applied to return data types in PostgreSQL |
|
|
Always null, since this information is not applied to return data types in PostgreSQL |
|
|
Always null, since this information is not applied to return data types in PostgreSQL |
|
|
Always null, since this information is not applied to return data types in PostgreSQL |
|
|
Always null, since this information is not applied to return data types in PostgreSQL |
|
|
Always null, since this information is not applied to return data types in PostgreSQL |
|
|
Always null, since this information is not applied to return data types in PostgreSQL |
|
|
Always null, since this information is not applied to return data types in PostgreSQL |
|
|
Always null, since this information is not applied to return data types in PostgreSQL |
|
|
Name of the database that the return data type of the function is defined in (always the current database) |
|
|
Name of the schema that the return data type of the function is defined in |
|
|
Name of the return data type of the function |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Always null, because arrays always have unlimited maximum cardinality in PostgreSQL |
|
|
An identifier of the data type descriptor of the return data type of this function, 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.) |
|
|
If the function is an SQL function, then |
|
|
The source text of the function (null if the function is not owned by a currently enabled role). (According to the SQL standard, this column is only applicable if |
|
|
If this function is a C function, then the external name (link symbol) of the function; else null. (This works out to be the same value that is shown in |
|
|
The language the function is written in |
|
|
Always |
|
|
If the function is declared immutable (called deterministic in the SQL standard), then |
|
|
Always |
|
|
If the function automatically returns null if any of its arguments are null, then |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Always |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
If the function runs with the privileges of the current user, then |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Currently always |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
|
|
Applies to a feature not available in PostgreSQL |
+
Prev | Up | Next |
---|---|---|
36.39. |
36.41. |
Copyright © 1996-2023 The PostgreSQL Global Development Group