Reword information_schema duplicate constraint warning text.

diff --git a/doc/src/sgml/information_schema.sgml b/doc/src/sgml/information_schema.sgml
index 32e9083744351c8e386900acc736c009918d7aa6..21e4f98913a5cd47408af82f1fb44b8e1a4c4de4 100644 (file)
--- a/doc/src/sgml/information_schema.sgml
+++ b/doc/src/sgml/information_schema.sgml
@@ -23,13 +23,14 @@
 
  
   
-   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. 
+   When querying the database for constraint information, it is possible
+   for a standard-compliant query that expects to return one row to
+   return several.  This is because the SQL standard requires constraint
+   names to be unique within a schema, but
+   PostgreSQL does not enforce this
+   restriction.  PostgreSQL
+   automatically-generated constraint names avoid duplicates in the
+   same schema, but users can specify such duplicate names.