Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id C2133B5DBD5 for ; Sat, 6 Aug 2011 12:06:09 -0300 (ADT) 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 64333-10 for ; Sat, 6 Aug 2011 15:06:04 +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 CE4FBB5D800 for ; Sat, 6 Aug 2011 12:06:03 -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 p76F5wbQ012176; Sat, 6 Aug 2011 11:05:58 -0400 (EDT) To: Dean Rasheed cc: Peter Eisentraut , Alvaro Herrera , Robert Haas , Pg Hackers Subject: Re: cataloguing NOT NULL constraints In-reply-to: References: <20110707213401.GA27098@alvh.no-ip.org> <1311291819-sup-6206@alvh.no-ip.org> <1311367030-sup-9426@alvh.no-ip.org> <1311985058-sup-952@alvh.no-ip.org> <1312342392-sup-7189@alvh.no-ip.org> <1312480674.24208.8.camel@vanquo.pezone.net> <1312624993.24721.16.camel@vanquo.pezone.net> Comments: In-reply-to Dean Rasheed message dated "Sat, 06 Aug 2011 12:58:53 +0100" Date: Sat, 06 Aug 2011 11:05:58 -0400 Message-ID: <12175.1312643158@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.831 tagged_above=-5 required=5 tests=BAYES_00=-1.9, RP_MATCHES_RCVD=-0.931 X-Spam-Level: X-Archive-Number: 201108/299 X-Sequence-Number: 193054 Dean Rasheed writes: > [ wonders what psql's \d will do with NOT NULL constraints ] I think this might be taking the notion of "it should be backwards compatible" too far. We're not expecting this patch to not change the wording of error messages, for instance (in fact, I think a large part of the point is to add constraint names to not-null errors). Why would we expect it to not change what \d shows? regards, tom lane