Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s58gh-003T3c-6A for pgsql-hackers@arkaria.postgresql.org; Thu, 09 May 2024 18:40:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1s58ge-009bIa-Ug for pgsql-hackers@arkaria.postgresql.org; Thu, 09 May 2024 18:40:13 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s58gd-009bIS-Q7 for pgsql-hackers@lists.postgresql.org; Thu, 09 May 2024 18:40:12 +0000 Received: from fhigh8-smtp.messagingengine.com ([103.168.172.159]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s58gY-000E2S-91 for pgsql-hackers@postgresql.org; Thu, 09 May 2024 18:40:11 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.48]) by mailfhigh.nyi.internal (Postfix) with ESMTP id D767A114014F; Thu, 9 May 2024 14:40:03 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Thu, 09 May 2024 14:40:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1715280003; x= 1715366403; bh=9Ei2RzIbRBA9IBtEcH1ToX6E1ujrN8fPsfae0rEGbU0=; b=S dqh+BS1ybCLQV0T/xl5L2nNUedM/rLhYSEAM2az8/dEEFbf5/S8ROPixxBS7YO7/ ndMt0H55L9ln4FXWXkdUwk31IYqMnQgR6ZZYDTqHO+Xf2l2GRUZid4WISoeWcqd3 wWyVOXJ9fwW1fngC238xJbBtkZtI80QIHXmOR4Wwc+HIaoD5RfRTyiOB0TdINYqO akHlCMBLpVGF85HpKhSfl84mtI3tV/RhIgbpT4Olgt7fDpuiEPes/ksBzoIOiGjD 7BGOTtcsANQmeTAklmq91FueEm7Kc/I9mW2uV9f2MXk2Lt73Em2XahvfCa/eaM1J p9B1EAQ+yvrYNTRiV+Huw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvdefvddguddviecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvvefukfggtggugfgjsehtkeertddttdejnecuhfhrohhmpemllhhv rghrohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorh hgqeenucggtffrrghtthgvrhhnpedvheeuffehgfeukeeufeehhefghfeugfefudekjeev udffgeffkeegffffveegheenucffohhmrghinhepvghnthgvrhhprhhishgvuggsrdgtoh hmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghl vhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 9 May 2024 14:40:03 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alvh.no-ip.org; s=schmee; t=1715280000; bh=3hsqoLRbtr8luGQJwp6KjEcXMTkhj2OEsKYrLB+zxq8=; h=Date:From:To:Cc:Subject:In-Reply-To:From; b=i4ifwqQNADzaxnSVOQ12UFwB6q0G0gi5m7IHoqHh73quJ8yi3WMQ+3w9lDySKo5kH cMVr3jHZ763F4DJpVwD/asCCLyQfkOaRexVkjD+72MKIHcLRDZoOIhLSeWWkBrolzI emTw19hwRdi9y/ncEXTO2g2wdK8zSY0n5MpA8x2AhrJMhUxNZo+VP2ZxHRC/1UXwJN OScSZemtP+mMr9PhiNFD+a9plqJ0941R0fH1RsQzmFZlEQ32JjH78j9oWw80qo+UVo KqYqSFlqAqFBlfSMbcUebcNvx69v+p4Y9JsXjVvFsbk5LT2H1j1C25Q2rc/CIwS3O3 vDVnqmvYBVDoA== Received: by schmee.alvh.no-ip.org (Postfix, from userid 1000) id 54B87F1; Thu, 9 May 2024 20:40:00 +0200 (CEST) Date: Thu, 9 May 2024 20:40:00 +0200 From: =?utf-8?Q?=C3=81lvaro?= Herrera To: Bruce Momjian Cc: jian he , PostgreSQL-development Subject: Re: First draft of PG 17 release notes Message-ID: <202405091840.6rbdffzmwmbz@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 2024-May-09, Bruce Momjian wrote: > However, I don't see it mentioned as a release note item in the commit > message or mentioned in our docs. I suppose the release note text would > be: > > Removing a PRIMARY KEY will remove the NOT NULL column specification > > Previously the NOT NULL specification would be retained. > > Do we have agreement that we want this release note item? Yes. Maybe we want some others too (especially regarding inheritance, but also regarding the way we handle the constraints internally), and maybe in this one we want different wording. How about something like this: Removing a primary key constraint may change the nullability characteristic of the columns that the primary key covered. If explicit not-null constraints exist on the same column, then they continue to be /known not nullable/; otherwise they become /possibly nullable/. This is largely based on the SQL standard's language of a column descriptor having a "nullability characteristic", which for columns with not-null or primary key constraints is "known not null". I don't think we use those terms anywhere. I hope this isn't too confusing. The standard's text on this, in section "4.13 Columns, fields, and attributes", is Every column has a nullability characteristic that indicates whether the value from that column can be the null value. A nullability characteristic is either known not nullable or possibly nullable. -- Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/