The view key_column_usage identifies all columns in the current database that are restricted by some unique, primary key, or foreign key constraint. Check constraints are not included in this view. Only those columns are shown that the current user has access to, by way of being the owner or having some privilege.
Table 34-29. key_column_usage Columns
|constraint_catalog||sql_identifier||Name of the database that contains the constraint (always the current database)|
|constraint_schema||sql_identifier||Name of the schema that contains the constraint|
|constraint_name||sql_identifier||Name of the constraint|
|table_catalog||sql_identifier||Name of the database that contains the table that contains the column that is restricted by this constraint (always the current database)|
|table_schema||sql_identifier||Name of the schema that contains the table that contains the column that is restricted by this constraint|
|table_name||sql_identifier||Name of the table that contains the column that is restricted by this constraint|
|column_name||sql_identifier||Name of the column that is restricted by this constraint|
|ordinal_position||cardinal_number||Ordinal position of the column within the constraint key (count starts at 1)|
|position_in_unique_constraint||cardinal_number||For a foreign-key constraint, ordinal position of the referenced column within its unique constraint (count starts at 1); otherwise null|
Please use this form to add your own comments regarding your experience with particular features of PostgreSQL, clarifications of the documentation, or hints for other users. Please note, this is not a support forum, and your IP address will be logged. If you have a question or need help, please see the faq, try a mailing list, or join us on IRC. Note that submissions containing URLs or other keywords commonly found in 'spam' comments may be silently discarded. Please contact the webmaster if you think this is happening to you in error.
Proceed to the comment form.