Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oaasJ-0004gV-W8 for pgsql-hackers@arkaria.postgresql.org; Tue, 20 Sep 2022 10:53:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oaasI-0003XE-Ra for pgsql-hackers@arkaria.postgresql.org; Tue, 20 Sep 2022 10:53:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oaasI-0003X4-I9 for pgsql-hackers@lists.postgresql.org; Tue, 20 Sep 2022 10:53:10 +0000 Received: from wout1-smtp.messagingengine.com ([64.147.123.24]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oaasF-00089y-VS for pgsql-hackers@lists.postgresql.org; Tue, 20 Sep 2022 10:53:10 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 13A6D3200945; Tue, 20 Sep 2022 06:53:04 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Tue, 20 Sep 2022 06:53:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; t=1663671184; x=1663757584; bh=G r6F2S1dW8nAeKu5vfEAB/k8QM33mnbfGsakiVQTen8=; b=CBv+2aCa0/Mbx7Wy+ c0zS5ODJE2bIlQaK0oIPTj/m9gePsUmRSwTDBMD0Ucj29vMzDCL2mhmj7SFChi9e Sle5wyMSkTWRwEMfvG66Jzc+Oj6Glx91/bNWeV0SXZJom5cO/E4hZ08Bp8G0CI9t 31Ri2pV+3Mhs4hUmjUeHSrUOXY/LChFpySxWl0h5IjazmrKUc8zo9Ntazh9jTXPz D7pJK1Zyrw6l4vIdrP25cmg+08UmFVrgPzsIBqXsjlshpRgAWvKZonWBwzr8MQBz HDv/eBdjnxZIExWADUFarzEuzuA7wUNEszmX5fHLhV6/PgAwIMcJs/fe068q4v0g LMS8A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrfedvledgfeegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkgggtugfgjgesthekredttddtjeenucfhrhhomheptehlvhgr rhhoucfjvghrrhgvrhgruceorghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh eqnecuggftrfgrthhtvghrnhepueeigfffueektdfgteeuuefgtedvueehgfehleefheel jeelfeffjedttdekvdejnecuffhomhgrihhnpehpohhsthhgrhdrvghspdgvnhhtvghrph hrihhsvggusgdrtghomhenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgr ihhlfhhrohhmpegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 20 Sep 2022 06:53:04 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id B02F738F; Tue, 20 Sep 2022 12:53:02 +0200 (CEST) Date: Tue, 20 Sep 2022 12:53:02 +0200 From: Alvaro Herrera To: Isaac Morland Cc: Robert Haas , Pg Hackers Subject: Re: cataloguing NOT NULL constraints Message-ID: <20220920105302.dyy2na6zfji4ded3@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2022-Sep-19, Isaac Morland wrote: > I thought I saw some discussion about the SQL standard saying that there is > a difference between putting NOT NULL in a column definition, and CHECK > (column_name NOT NULL). So if we're going to take this seriously, Was it Peter E.'s reply to this thread? https://postgr.es/m/bac841ed-b86d-e3c2-030d-02a3db067307@enterprisedb.com because if it wasn't there, then I would like to know what you source is. -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/ "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end." (2nd Commandment for C programmers)