|
21 | 21 | <productname>PostgreSQL</productname>-specific views. |
22 | 22 | </para> |
23 | 23 |
|
| 24 | + <note> |
| 25 | + <para> |
| 26 | + The SQL standard requires constraint names to be unique within a |
| 27 | + schema; <productname>PostgreSQL</productname>, however, does not |
| 28 | + enforce this restriction. If duplicate-named constraints are |
| 29 | + stored in the same <productname>PostgreSQL</productname> schema, |
| 30 | + a standard-compliant query that expects to return one matching |
| 31 | + constraint row might return several, one row for each matching |
| 32 | + constraint stored in the specified schema. |
| 33 | + </para> |
| 34 | + </note> |
| 35 | + |
| 36 | + |
24 | 37 | <sect1 id="infoschema-schema"> |
25 | 38 | <title>The Schema</title> |
26 | 39 |
|
@@ -3212,18 +3225,6 @@ ORDER BY c.ordinal_position; |
3212 | 3225 | </tgroup> |
3213 | 3226 | </table> |
3214 | 3227 |
|
3215 | | - <note> |
3216 | | - <para> |
3217 | | - The SQL standard requires constraint names to be unique within a |
3218 | | - schema; <productname>PostgreSQL</productname>, however, does not |
3219 | | - enforce this restriction. If duplicate-named constraints are |
3220 | | - stored in the same <productname>PostgreSQL</productname> schema, a |
3221 | | - standard-compliant query that expects to return one row might |
3222 | | - return several, one for each matching constraint stored in the |
3223 | | - specified schema. |
3224 | | - </para> |
3225 | | - </note> |
3226 | | - |
3227 | 3228 | </sect1> |
3228 | 3229 |
|
3229 | 3230 | <sect1 id="infoschema-role-column-grants"> |
|