From: Bruce Momjian <bruce@momjian.us>
Date: Wed, 23 Feb 2011 04:31:45 +0000 (-0500)
Subject: Update wording about information schema and name which views potentially
X-Git-Tag: REL9_1_ALPHA4~110
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=2c72d7042bc09bd8a1f2dc8ab288fec449760ba8;p=thirdparty%2Fpostgresql.git

Update wording about information schema and name which views potentially
can have duplicates, per request from Tom.
---

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>