diff options
| author | Bruce Momjian <bruce@momjian.us> | 2011-02-22 23:31:45 -0500 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2011-02-22 23:32:23 -0500 |
| commit | 2c72d7042bc09bd8a1f2dc8ab288fec449760ba8 (patch) | |
| tree | 1416ab33370bb36c8dd4018a02ba312a5d491b1c | |
| parent | 5a922f13eff66b3e437e823419d48d509d59a6be (diff) | |
| download | postgresql-2c72d7042bc09bd8a1f2dc8ab288fec449760ba8.tar.gz postgresql-2c72d7042bc09bd8a1f2dc8ab288fec449760ba8.zip | |
Update wording about information schema and name which views potentially
can have duplicates, per request from Tom.
| -rw-r--r-- | doc/src/sgml/information_schema.sgml | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/src/sgml/information_schema.sgml b/doc/src/sgml/information_schema.sgml index 21e4f98913a..aa6f852a8a3 100644 --- a/doc/src/sgml/information_schema.sgml +++ b/doc/src/sgml/information_schema.sgml @@ -32,6 +32,16 @@ automatically-generated constraint names avoid duplicates in the same schema, but users can specify such duplicate names. </para> + + <para> + This problem can appear when querying information schema views like + <literal>referential_constraints</>, <literal>check_constraints</>, + <literal>domain_constraints</>, and + <literal>check_constraint_routine_usage</>. Some other views have + similar issues but contain the table name to help distinguish + duplicate rows, e.g. <literal>table_constraints</>, + <literal>constraint_table_usage</>, <literal>constraint_column_usage</>. + </para> </note> |