aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorPeter Eisentraut <peter@eisentraut.org>2023-12-01 08:40:45 +0100
committerPeter Eisentraut <peter@eisentraut.org>2023-12-01 08:41:41 +0100
commit5b2dcead39904ae56e2c17cb5c7a14e6f255790c (patch)
tree6c73fcd5c276d064301e931a6e947d21365a8aed /doc/src
parentf66fcc5cd616da8d81a2d2f9b80a9f080796f4b6 (diff)
downloadpostgresql-5b2dcead39904ae56e2c17cb5c7a14e6f255790c.tar.gz
postgresql-5b2dcead39904ae56e2c17cb5c7a14e6f255790c.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
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/information_schema.sgml30
1 files changed, 16 insertions, 14 deletions
diff --git a/doc/src/sgml/information_schema.sgml b/doc/src/sgml/information_schema.sgml
index 9c39e9aab50..0ca7d5a9e0b 100644
--- a/doc/src/sgml/information_schema.sgml
+++ b/doc/src/sgml/information_schema.sgml
@@ -4846,9 +4846,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>
@@ -5085,12 +5087,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>
@@ -5184,11 +5186,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>