Skip to content

Commit e07ae21

Browse files
committed
Document that an SQL-standard-compliant query that expects a unique row
from information_schema.referential_constraints might return several in Postgres because we allow duplicate-named constraints in the same schema.
1 parent b05186f commit e07ae21

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

doc/src/sgml/information_schema.sgml

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3211,6 +3211,19 @@ ORDER BY c.ordinal_position;
32113211
</tbody>
32123212
</tgroup>
32133213
</table>
3214+
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+
32143227
</sect1>
32153228

32163229
<sect1 id="infoschema-role-column-grants">

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy