PostgreSQL
53.39. pg_proc
The catalog pg_proc
stores information about functions, procedures, aggregate functions, and window functions (collectively also known as routines). See CREATE FUNCTION, CREATE PROCEDURE, and Section 38.3 for more information.
If prokind
indicates that the entry is for an aggregate function, there should be a matching row in pg_aggregate
.
Table 53.39. pg_proc
Columns
Column Type Description |
---|
Row identifier |
Name of the function |
The OID of the namespace that contains this function |
Owner of the function |
Implementation language or call interface of this function |
Estimated execution cost (in units of cpu_operator_cost); if |
Estimated number of result rows (zero if not |
Data type of the variadic array parameter’s elements, or zero if the function does not have a variadic parameter |
Planner support function for this function (see Section 38.11), or zero if none |
|
Function is a security definer (i.e., a “[.quote]#setuid”# function) |
The function has no side effects. No information about the arguments is conveyed except via the return value. Any function that might throw an error depending on the values of its arguments is not leak-proof. |
Function returns null if any call argument is null. In that case the function won’t actually be called at all. Functions that are not “[.quote]#strict”# must be prepared to handle null inputs. |
Function returns a set (i.e., multiple values of the specified data type) |
|
|
Number of input arguments |
Number of arguments that have defaults |
Data type of the return value |
An array of the data types of the function arguments. This includes only input arguments (including |
An array of the data types of the function arguments. This includes all arguments (including |
An array of the modes of the function arguments, encoded as |
An array of the names of the function arguments. Arguments without a name are set to empty strings in the array. If none of the arguments have a name, this field will be null. Note that subscripts correspond to positions of |
Expression trees (in |
An array of the argument/result data type(s) for which to apply transforms (from the function’s |
This tells the function handler how to invoke the function. It might be the actual source code of the function for interpreted languages, a link symbol, a file name, or just about anything else, depending on the implementation language/call convention. |
Additional information about how to invoke the function. Again, the interpretation is language-specific. |
Pre-parsed SQL function body. This is used for SQL-language functions when the body is given in SQL-standard notation rather than as a string literal. It’s null in other cases. |
Function’s local settings for run-time configuration variables |
Access privileges; see Section 5.7 for details |
+
For compiled functions, both built-in and dynamically loaded, prosrc
contains the function’s C-language name (link symbol). For SQL-language functions, prosrc
contains the function’s source text if that is specified as a string literal; but if the function body is specified in SQL-standard style, prosrc
is unused (typically it’s an empty string) and prosqlbody
contains the pre-parsed definition. For all other currently-known language types, prosrc
contains the function’s source text. probin
is null except for dynamically-loaded C functions, for which it gives the name of the shared library file containing the function.
Prev | Up | Next |
---|---|---|
53.38. |
53.40. |
Submit correction
If you see anything in the documentation that is not correct, does not match your experience with the particular feature or requires further clarification, please use this form to report a documentation issue.
Copyright © 1996-2023 The PostgreSQL Global Development Group