diff options
| -rw-r--r-- | doc/src/sgml/information_schema.sgml | 15 |
1 files changed, 8 insertions, 7 deletions
diff --git a/doc/src/sgml/information_schema.sgml b/doc/src/sgml/information_schema.sgml index 32e90837443..21e4f98913a 100644 --- a/doc/src/sgml/information_schema.sgml +++ b/doc/src/sgml/information_schema.sgml @@ -23,13 +23,14 @@ <note> <para> - The SQL standard requires constraint names to be unique within a - schema; <productname>PostgreSQL</productname>, however, does not - enforce this restriction. If duplicate-named constraints are - stored in the same <productname>PostgreSQL</productname> 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 + <productname>PostgreSQL</productname> does not enforce this + restriction. <productname>PostgreSQL</productname> + automatically-generated constraint names avoid duplicates in the + same schema, but users can specify such duplicate names. </para> </note> |