Received: from maia.hub.org (maia-2.hub.org [200.46.204.251])
	by mail.postgresql.org (Postfix) with ESMTP id 915F4635E1B
	for <pgsql-docs-postgresql.org@mail.postgresql.org>;
	Tue,  7 Sep 2010 11:49:28 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia,
	port 10024) with ESMTP id 23313-06-2 for
	<pgsql-docs-postgresql.org@mail.postgresql.org>;
	Tue,  7 Sep 2010 14:49:19 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22])
	by mail.postgresql.org (Postfix) with SMTP id 11714634C80
	for <pgsql-docs@postgreSQL.org>; Tue,  7 Sep 2010 11:49:12 -0300 (ADT)
Received: (qmail invoked by alias); 07 Sep 2010 14:49:10 -0000
Received: from a88-115-218-165.elisa-laajakaista.fi (EHLO [10.0.0.101])
	[88.115.218.165]
	by mail.gmx.net (mp050) with SMTP; 07 Sep 2010 16:49:10 +0200
X-Authenticated: #495269
X-Provags-ID: V01U2FsdGVkX1+ypaQbfUKy5fiDNWGsJsCuoOwn7cdPitJUc02GGw
	o3HClj9VjyYFN8
Subject: Re: [BUGS] issue about information_schema
 REFERENTIAL_CONSTRAINTS
From: Peter Eisentraut <peter_e@gmx.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@commandprompt.com>, Fabien COELHO
	<coelho@cri.ensmp.fr>, pgsql-docs@postgreSQL.org
In-Reply-To: <5762.1283739417@sss.pgh.pa.us>
References: <alpine.DEB.2.00.1008311337530.2449@localhost.localdomain>
	<2683.1283266019@sss.pgh.pa.us>
	<alpine.DEB.2.00.1009011557480.2570@localhost.localdomain>
	<1283369900.15386.0.camel@vanquo.pezone.net>
	<alpine.DEB.2.00.1009020741380.2656@localhost.localdomain>
	<1283438419.23199.0.camel@vanquo.pezone.net>
	<alpine.DEB.2.00.1009021959070.2656@localhost.localdomain>
	<6462.1283454730@sss.pgh.pa.us>
	<alpine.DEB.2.00.1009031348321.2448@localhost.localdomain>
	<22801.1283525905@sss.pgh.pa.us>
	<alpine.DEB.2.00.1009031920460.2622@localhost.localdomain>
	<1283535870-sup-2648@alvh.no-ip.org> <26284.1283536406@sss.pgh.pa.us>
	<1283712463.12666.7.camel@vanquo.pezone.net>
	<5762.1283739417@sss.pgh.pa.us>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 07 Sep 2010 17:49:06 +0300
Message-ID: <1283870946.2517.9.camel@vanquo.pezone.net>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.2 
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
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,
	RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201009/42
X-Sequence-Number: 6032

On sön, 2010-09-05 at 22:16 -0400, Tom Lane wrote:
> > A very similar issue is already documented here:
> > http://developer.postgresql.org/pgdocs/postgres/infoschema-triggers.html
> 
> That sort of annotation was my first thought, but we'd have to repeat
> ourselves in multiple places because there are several views that are
> affected by the constraint-name issue.  (Come to think of it, isn't
> triggered_update_columns also affected by the trigger-name issue?)
> 
> 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.