Move information_schema duplicate constraint note to the top of the

information schema documentation because it affects several tables.

diff --git a/doc/src/sgml/information_schema.sgml b/doc/src/sgml/information_schema.sgml
index 91c2dd4d525f424f4370776bfd2c23482d4023ad..32e9083744351c8e386900acc736c009918d7aa6 100644 (file)
--- a/doc/src/sgml/information_schema.sgml
+++ b/doc/src/sgml/information_schema.sgml
@@ -21,6 +21,19 @@
   PostgreSQL-specific views.
  
 
+ 
+  
+   The SQL standard requires constraint names to be unique within a
+   schema;  PostgreSQL, however, does not
+   enforce this restriction.  If duplicate-named constraints are
+   stored in the same PostgreSQL schema,
+   a standard-compliant query that expects to return one matching
+   constraint row might return several, one row for each matching
+   constraint stored in the specified schema. 
+  
+ 
+
+
  
   The Schema
 
@@ -3212,18 +3225,6 @@ ORDER BY c.ordinal_position;
    
   
 
-  
-   
-    The SQL standard requires constraint names to be unique within a
-    schema;  PostgreSQL, however, does not
-    enforce this restriction.  If duplicate-named constraints are
-    stored in the same PostgreSQL schema, a
-    standard-compliant query that expects to return one row might
-    return several, one for each matching constraint stored in the
-    specified schema.
-   
-  
-