Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id DD817632AD6 for ; Fri, 3 Sep 2010 14:39:38 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 11766-06 for ; Fri, 3 Sep 2010 17:39:24 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from cascavel.ensmp.fr (cascavel.ensmp.fr [194.214.158.227]) by mail.postgresql.org (Postfix) with ESMTP id F0F9F6310AC for ; Fri, 3 Sep 2010 14:39:23 -0300 (ADT) Received: from cri.ensmp.fr (85.40.219-88.rev.gaoland.net [88.219.40.85] (may be forged)) (authenticated bits=0) by cascavel.ensmp.fr (8.14.3/8.14.3/JMMC-11/Mar/2010) with ESMTP id o83HdK6X019247 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Sep 2010 19:39:21 +0200 (MEST) Date: Fri, 3 Sep 2010 19:39:19 +0200 (CEST) From: Fabien COELHO X-X-Sender: fabien@localhost.localdomain Reply-To: Fabien COELHO To: Tom Lane cc: Peter Eisentraut , PostgreSQL Bugs List Subject: Re: issue about information_schema REFERENTIAL_CONSTRAINTS In-Reply-To: <22801.1283525905@sss.pgh.pa.us> Message-ID: References: <2683.1283266019@sss.pgh.pa.us> <1283369900.15386.0.camel@vanquo.pezone.net> <1283438419.23199.0.camel@vanquo.pezone.net> <6462.1283454730@sss.pgh.pa.us> <22801.1283525905@sss.pgh.pa.us> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Miltered: at cascavel with ID 4C8132C8.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 4C8132C8.000 from [88.219.40.85]/85.40.219-88.rev.gaoland.net/88.219.40.85/cri.ensmp.fr/ X-Scores-Stats: 4C8132C8.000 B=0.02163 L=0.16237 G=0.00427 Agree X-j-chkmail-Score: MSGID : 4C8132C8.000 on cascavel.ensmp.fr : j-chkmail score : . : R=. U=. O=. B=0.004 -> S=0.005 X-j-chkmail-Status: Ham 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/27 X-Sequence-Number: 27991 >> Well, one must choose between to evil: > > Yeah, exactly. I think that the current tradeoff is just fine. Hmmm. I think exactly the contrary. There is no point in having a non reliable feature. ISTM that very few people use the information schema, and if the query results is not reliable, it will stay this way. If you have zero user, no one will complain, which prooves that everything is fine:-) QED. By the way, do you use the information schema? > If you want SQL-standard behavior, pick SQL-standard constraint names, > and there you are. I tried to explained that I'm analyzing other people's schemas. I cannot ask all other people on the planet to rewrite their schemas, I pick them as they are. Could you register this "bug" somewhere please? Thanks for your time. -- Fabien.