Received: from maia.hub.org (maia-2.hub.org [200.46.204.251])
	by mail.postgresql.org (Postfix) with ESMTP id 4B3BD6329DF
	for <pgsql-bugs-postgresql.org@mail.postgresql.org>;
	Fri,  3 Sep 2010 11:58:43 -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 40448-03 for
	<pgsql-bugs-postgresql.org@mail.postgresql.org>;
	Fri,  3 Sep 2010 14:58:31 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by mail.postgresql.org (Postfix) with ESMTP id 8EBEE6318F3
	for <pgsql-bugs@postgresql.org>; Fri,  3 Sep 2010 11:58:32 -0300 (ADT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id o83EwPrK022802;
	Fri, 3 Sep 2010 10:58:25 -0400 (EDT)
To: Fabien COELHO <coelho@cri.ensmp.fr>
cc: Peter Eisentraut <peter_e@gmx.net>,
	PostgreSQL Bugs List <pgsql-bugs@postgresql.org>
Subject: Re: issue about information_schema REFERENTIAL_CONSTRAINTS 
In-reply-to: <alpine.DEB.2.00.1009031348321.2448@localhost.localdomain> 
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>
Comments: In-reply-to Fabien COELHO <coelho@cri.ensmp.fr>
	message dated "Fri, 03 Sep 2010 14:08:36 +0200"
Date: Fri, 03 Sep 2010 10:58:25 -0400
Message-ID: <22801.1283525905@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
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: 201009/25
X-Sequence-Number: 27989

Fabien COELHO <coelho@cri.ensmp.fr> writes:
>> Note that (2) fails for long names; you have to do something to
>> compress to NAMEDATALEN.

> Indeed.

> What if the type is changed to TEXT? It is just a view after all.
> How important is it to stick to "sql_identifier"?

It's a view defined by the SQL standard, and one of the properties
defined by the standard is the type of that column.

> Well, one must choose between to evil:

Yeah, exactly.  I think that the current tradeoff is just fine.
If you want SQL-standard behavior, pick SQL-standard constraint names,
and there you are.

			regards, tom lane