pg_proc

The catalog pg_proc stores information about functions, procedures, aggregate functions, and window functions (collectively also known as routines).

Reading PG 18current·documented in 24 of 24 versions, 7.4 to 20

7.4 8.0 8.1 8.2 8.3 8.4 9.0 9.1 9.2 9.3 9.4 9.5 9.6 10 11 12 13 14 15 16 17 18 19 20

Kind: System catalogs
Columns in this snapshot: 30
Definition source: English manual
Metadata snapshot: 18.6

Columns 30

As listed in the PostgreSQL 18 manual.

Column	Type	Description / reference
`oid`	`oid`NOT NULL	Row identifier
`proname`	`name`NOT NULL	Name of the function
`pronamespace`	`oid`NOT NULL	The OID of the namespace that contains this function pg_namespace.oid
`proowner`	`oid`NOT NULL	Owner of the function pg_authid.oid
`prolang`	`oid`NOT NULL	Implementation language or call interface of this function pg_language.oid
`procost`	`float4`NOT NULL	Estimated execution cost (in units of cpu_operator_cost); if proretset, this is cost per row returned
`prorows`	`float4`NOT NULL	Estimated number of result rows (zero if not proretset)
`provariadic`	`oid`NOT NULL	Data type of the variadic array parameter's elements, or zero if the function does not have a variadic parameter pg_type.oid
`prosupport`	`regproc`NOT NULL	Planner support function for this function (see Section 36.11), or zero if none pg_proc.oid
`prokind`	`char`NOT NULL	f for a normal function, p for a procedure, a for an aggregate function, or w for a window function
`prosecdef`	`bool`NOT NULL	Function is a security definer (i.e., a “setuid” function)
`proleakproof`	`bool`NOT NULL	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 leakproof.
`proisstrict`	`bool`NOT NULL	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 “strict” must be prepared to handle null inputs.
`proretset`	`bool`NOT NULL	Function returns a set (i.e., multiple values of the specified data type)
`provolatile`	`char`NOT NULL	provolatile tells whether the function's result depends only on its input arguments, or is affected by outside factors. It is i for “immutable” functions, which always deliver the same result for the same inputs. It is s for “stable” functions, whose results (for fixed inputs) do not change within a scan. It is v for “volatile” functions, whose results might change at any time. (Use v also for functions with side-effects, so that calls to them cannot get optimized away.)
`proparallel`	`char`NOT NULL	proparallel tells whether the function can be safely run in parallel mode. It is s for functions which are safe to run in parallel mode without restriction. It is r for functions which can be run in parallel mode, but their execution is restricted to the parallel group leader; parallel worker processes cannot invoke these functions. It is u for functions which are unsafe in parallel mode; the presence of such a function forces a serial execution plan.
`pronargs`	`int2`NOT NULL	Number of input arguments
`pronargdefaults`	`int2`NOT NULL	Number of arguments that have defaults
`prorettype`	`oid`NOT NULL	Data type of the return value pg_type.oid
`proargtypes`	`oidvector`NOT NULL	An array of the data types of the function arguments. This includes only input arguments (including INOUT and VARIADIC arguments), and thus represents the call signature of the function. pg_type.oid
`proallargtypes`	`oid[]`	An array of the data types of the function arguments. This includes all arguments (including OUT and INOUT arguments); however, if all the arguments are IN arguments, this field will be null. Note that subscripting is 1-based, whereas for historical reasons proargtypes is subscripted from 0. pg_type.oid
`proargmodes`	`char[]`	An array of the modes of the function arguments, encoded as i for IN arguments, o for OUT arguments, b for INOUT arguments, v for VARIADIC arguments, t for TABLE arguments. If all the arguments are IN arguments, this field will be null. Note that subscripts correspond to positions of proallargtypes not proargtypes.
`proargnames`	`text[]`	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 proallargtypes not proargtypes.
`proargdefaults`	`pg_node_tree`	Expression trees (in nodeToString() representation) for default values. This is a list with pronargdefaults elements, corresponding to the last N input arguments (i.e., the last N proargtypes positions). If none of the arguments have defaults, this field will be null.
`protrftypes`	`oid[]`	An array of the argument/result data type(s) for which to apply transforms (from the function's TRANSFORM clause). Null if none. pg_type.oid
`prosrc`	`text`NOT NULL	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.
`probin`	`text`	Additional information about how to invoke the function. Again, the interpretation is language-specific.
`prosqlbody`	`pg_node_tree`	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.
`proconfig`	`text[]`	Function's local settings for run-time configuration variables
`proacl`	`aclitem[]`	Access privileges; see Section 5.8 for details