PostgreSQL 7.4beta4 Documentation
Prev | Fast Backward | Chapter 32. The Information Schema | Fast Forward | Next

# 32.19. parameters

The view parameters contains information about the parameters (arguments) 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 32-17. parameters Columns

Name | Data Type | Description
--- | --- | ---
specific_catalog | `sql_identifier` | Name of the database containing the function (always the current database)
specific_schema | `sql_identifier` | Name of the schema containing the function
specific_name | `sql_identifier` | The "specific name" of the function. See Section 32.26 for more information.
ordinal_position | `cardinal_number` | Ordinal position of the parameter in the argument list of the function (count starts at 1)
parameter_mode | `character_data` | Always IN, meaning input parameter (In the future there might be other parameter modes.)
is_result | `character_data` | Applies to a feature not available in PostgreSQL
as_locator | `character_data` | Applies to a feature not available in PostgreSQL
parameter_name | `sql_identifier` | Always null, since PostgreSQL does not support named parameters
data_type | `character_data` | Data type of the parameter, if it is a built-in type, or ARRAY if it is some array (in that case, see the view element_types), else USER-DEFINED (in that case, the type is identified in udt_name and associated columns).
character_maximum_length | `cardinal_number` | Always null, since this information is not applied to parameter data types in PostgreSQL
character_octet_length | `cardinal_number` | Always null, since this information is not applied to parameter data types in PostgreSQL
character_set_catalog | `sql_identifier` | Applies to a feature not available in PostgreSQL
character_set_schema | `sql_identifier` | Applies to a feature not available in PostgreSQL
character_set_name | `sql_identifier` | Applies to a feature not available in PostgreSQL
collation_catalog | `sql_identifier` | Applies to a feature not available in PostgreSQL
collation_schema | `sql_identifier` | Applies to a feature not available in PostgreSQL
collation_name | `sql_identifier` | Applies to a feature not available in PostgreSQL
numeric_precision | `cardinal_number` | Always null, since this information is not applied to parameter data types in PostgreSQL
numeric_precision_radix | `cardinal_number` | Always null, since this information is not applied to parameter data types in PostgreSQL
numeric_scale | `cardinal_number` | Always null, since this information is not applied to parameter data types in PostgreSQL
datetime_precision | `cardinal_number` | Always null, since this information is not applied to parameter data types in PostgreSQL
interval_type | `character_data` | Always null, since this information is not applied to parameter data types in PostgreSQL
interval_precision | `character_data` | Always null, since this information is not applied to parameter data types in PostgreSQL
udt_catalog | `sql_identifier` | Name of the database that the data type of the parameter is defined in (always the current database)
udt_schema | `sql_identifier` | Name of the schema that the data type of the parameter is defined in
udt_name | `sql_identifier` | Name of the data type of the parameter
scope_catalog | `sql_identifier` | Applies to a feature not available in PostgreSQL
scope_schema | `sql_identifier` | Applies to a feature not available in PostgreSQL
scope_name | `sql_identifier` | Applies to a feature not available in PostgreSQL
maximum_cardinality | `cardinal_number` | Always null, because arrays always have unlimited maximum cardinality in PostgreSQL
dtd_identifier | `sql_identifier` | 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.)

Prev | Home | Next
key_column_usage | Up | referential_constraints