Received: from maia.hub.org (maia-3.hub.org [200.46.204.243])
	by mail.postgresql.org (Postfix) with ESMTP id F2A1F1337990
	for <pgsql-docs-postgresql.org@mail.postgresql.org>;
	Sun, 20 Feb 2011 03:54:11 -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 80947-04 for
	<pgsql-docs-postgresql.org@mail.postgresql.org>;
	Sun, 20 Feb 2011 07:54:04 +0000 (UTC)
X-Greylist: delayed 00:05:27.837547 by SQLgrey-1.7.6
Received: from smtp-3.ensmp.fr (smtp-3.ensmp.fr [194.214.158.227])
	by mail.postgresql.org (Postfix) with ESMTP id 363B31336FA7
	for <pgsql-docs@postgresql.org>; Sun, 20 Feb 2011 03:54:04 -0400 (AST)
Received: from cri.ensmp.fr (184.40.219-88.rev.gaoland.net [88.219.40.184]
	(may be forged)) (authenticated bits=0)
	by smtp-3.ensmp.fr (8.14.3/8.14.3/JMMC-11/Mar/2010) with ESMTP id
	p1K7mMI9004826
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Sun, 20 Feb 2011 08:48:22 +0100 (MET)
Date: Sun, 20 Feb 2011 08:48:21 +0100 (CET)
From: Fabien COELHO <coelho@cri.ensmp.fr>
X-X-Sender: fabien@localhost6.localdomain6
Reply-To: Fabien COELHO <coelho@cri.ensmp.fr>
To: Bruce Momjian <bruce@momjian.us>
cc: Peter Eisentraut <peter_e@gmx.net>, Tom Lane <tgl@sss.pgh.pa.us>,
	Alvaro Herrera <alvherre@commandprompt.com>, pgsql-docs@postgresql.org
Subject: Re: [BUGS] issue about information_schema
 REFERENTIAL_CONSTRAINTS
In-Reply-To: <201102200011.p1K0B1l06164@momjian.us>
Message-ID: <alpine.DEB.2.00.1102200825550.2423@localhost6.localdomain6>
References: <201102200011.p1K0B1l06164@momjian.us>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Miltered: at cascavel with ID 4D60C746.000 by Joe's j-chkmail (http : //
	j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 4D60C746.000 from
	[88.219.40.184]/184.40.219-88.rev.gaoland.net/88.219.40.184/cri.ensmp.fr/<coelho@cri.ensmp.fr>
X-Scores-Stats: 4D60C746.000 B=0.00632 L=0.30040 G=0.00272 Agree    
X-j-chkmail-Score: MSGID : 4D60C746.000 on smtp-3.ensmp.fr : j-chkmail score :
	. : R=. U=. O=. B=0.003 -> S=0.003
X-j-chkmail-Status: Ham
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.62 tagged_above=-5 required=5 tests=BAYES_00=-1.9,
	MAY_BE_FORGED=0.29, T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201102/64
X-Sequence-Number: 6412


Hello Bruce,

>>>> Is that the direction we want to go, or would it be better to factor
>>>> the information out into a separate page about compatibility gotchas?
>>>
>>> It would probably be better to explain globally applicable issues in a
>>> separate section.
>>
>> I agree that a general caveat is better, together with a one line
>> reference in the documentation of each table with an issue.
>
> Oh, I just noticed this.  Can you give me a list of information_schema
> tables that have this issue?  I am only aware of
> referential_constraints.

Possibly any relation which references constraints with a (catalog, 
schema, name) triplet expecting it to be unique should have this issue.