diff options
| author | Peter Eisentraut <peter@eisentraut.org> | 2023-12-01 08:40:45 +0100 |
|---|---|---|
| committer | Peter Eisentraut <peter@eisentraut.org> | 2023-12-01 08:44:14 +0100 |
| commit | 1a4d714e18127264abf856fc6c07e056bd2f558a (patch) | |
| tree | 6d5d68ea3ad3efa3cd6f03f21dceb5f7d064966d | |
| parent | b2b1f12882fb561c7d474b834044dd8ed570bfea (diff) | |
| download | postgresql-1a4d714e18127264abf856fc6c07e056bd2f558a.tar.gz postgresql-1a4d714e18127264abf856fc6c07e056bd2f558a.zip | |
doc: Update info on information schema usage tables
Commit f40c6969d0 added the information schema usage tables but added
documentation that they did not fully work yet. Commit e717a9a18b
then added SQL-standard function bodies, which made the information
schema views fully functional, but it neglected to update the
documentation. This is now done here.
Reported-by: Erki Eessaar <erki.eessaar@taltech.ee>
Reviewed-by: Erki Eessaar <erki.eessaar@taltech.ee>
Discussion: https://www.postgresql.org/message-id/flat/AM9PR01MB8268EC7B696F9FE346CA5B93FEB8A%40AM9PR01MB8268.eurprd01.prod.exchangelabs.com
| -rw-r--r-- | doc/src/sgml/information_schema.sgml | 30 |
1 files changed, 16 insertions, 14 deletions
diff --git a/doc/src/sgml/information_schema.sgml b/doc/src/sgml/information_schema.sgml index 41001982528..45c9705cb1d 100644 --- a/doc/src/sgml/information_schema.sgml +++ b/doc/src/sgml/information_schema.sgml @@ -4845,9 +4845,11 @@ ORDER BY c.ordinal_position; <title><literal>routine_column_usage</literal></title> <para> - The view <literal>routine_column_usage</literal> is meant to identify all - columns that are used by a function or procedure. This information is - currently not tracked by <productname>PostgreSQL</productname>. + The view <literal>routine_column_usage</literal> identifies all columns + that are used by a function or procedure, either in the SQL body or in + parameter default expressions. (This only works for unquoted SQL bodies, + not quoted bodies or functions in other languages.) A column is only + included if its table is owned by a currently enabled role. </para> <table> @@ -5084,12 +5086,12 @@ ORDER BY c.ordinal_position; <title><literal>routine_routine_usage</literal></title> <para> - The view <literal>routine_routine_usage</literal> is meant to identify all - functions or procedures that are used by another (or the same) function or - procedure, either in the body or in parameter default expressions. - Currently, only functions used in parameter default expressions are - tracked. An entry is included here only if the used function is owned by a - currently enabled role. (There is no such restriction on the using + The view <literal>routine_routine_usage</literal> identifies all functions + or procedures that are used by another (or the same) function or procedure, + either in the SQL body or in parameter default expressions. (This only + works for unquoted SQL bodies, not quoted bodies or functions in other + languages.) An entry is included here only if the used function is owned + by a currently enabled role. (There is no such restriction on the using function.) </para> @@ -5183,11 +5185,11 @@ ORDER BY c.ordinal_position; <title><literal>routine_sequence_usage</literal></title> <para> - The view <literal>routine_sequence_usage</literal> is meant to identify all - sequences that are used by a function or procedure, either in the body or - in parameter default expressions. Currently, only sequences used in - parameter default expressions are tracked. A sequence is only included if - that sequence is owned by a currently enabled role. + The view <literal>routine_sequence_usage</literal> identifies all sequences + that are used by a function or procedure, either in the SQL body or in + parameter default expressions. (This only works for unquoted SQL bodies, + not quoted bodies or functions in other languages.) A sequence is only + included if that sequence is owned by a currently enabled role. </para> <table> |