Received: from maia.hub.org (maia-3.hub.org [200.46.204.243])
	by mail.postgresql.org (Postfix) with ESMTP id C449A1336B42
	for <pgsql-docs-postgresql.org@mail.postgresql.org>;
	Tue, 22 Feb 2011 10:07:59 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia,
	port 10024) with ESMTP id 74176-10 for
	<pgsql-docs-postgresql.org@mail.postgresql.org>;
	Tue, 22 Feb 2011 14:07:52 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from momjian.us (momjian.us [70.90.9.53])
	by mail.postgresql.org (Postfix) with ESMTP id 4E2BE1336971
	for <pgsql-docs@postgresql.org>; Tue, 22 Feb 2011 10:07:52 -0400 (AST)
Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id
 p1ME7dA17560;
	Tue, 22 Feb 2011 09:07:39 -0500 (EST)
From: Bruce Momjian <bruce@momjian.us>
Message-Id: <201102221407.p1ME7dA17560@momjian.us>
Subject: Re: [BUGS] issue about information_schema
 REFERENTIAL_CONSTRAINTS
In-Reply-To: 
To: bruce@momjian.us
Date: Tue, 22 Feb 2011 09:07:39 -0500 (EST)
CC: Fabien COELHO <coelho@cri.ensmp.fr>, Peter Eisentraut <peter_e@gmx.net>,
	Tom Lane <tgl@sss.pgh.pa.us>, Alvaro Herrera <alvherre@commandprompt.com>,
	pgsql-docs@postgresql.org
X-Mailer: ELM [version 2.4ME+ PL124 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.91 tagged_above=-5 required=5 tests=BAYES_00=-1.9,
	T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201102/75
X-Sequence-Number: 6423

bruce wrote:
> 
> I have moved the text about duplicate constraints to the top of the
> information schema section because it affects several tables (applied
> patch attached).  I could not figure out how to get the actual error
> concept to the front of the paragraph.

I found a way to reword the paragraph to be clearer about its purpose:

   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.

Applied.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +