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 1pjzeV-0008QC-4R for pgsql-hackers@arkaria.postgresql.org; Wed, 05 Apr 2023 09:42:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pjzeT-0000p4-ME for pgsql-hackers@arkaria.postgresql.org; Wed, 05 Apr 2023 09:42:01 +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 1pjzeS-0000ot-Tg for pgsql-hackers@lists.postgresql.org; Wed, 05 Apr 2023 09:42:01 +0000 Received: from new4-smtp.messagingengine.com ([66.111.4.230]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pjzeK-0010h1-DE for pgsql-hackers@postgresql.org; Wed, 05 Apr 2023 09:42:00 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailnew.nyi.internal (Postfix) with ESMTP id 5C78C581FDE for ; Wed, 5 Apr 2023 05:41:49 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Wed, 05 Apr 2023 05:41:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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:references :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=1680687709; x= 1680694909; bh=18LDFO5sEnwim88qk9GUlDAjbtPCy2fsUlv6bUh9kik=; b=W pe27VvcwCVA2NjDlEEzQ1m/u4zgATfQyyOfM7tTjO9IiHsEzW1omm2takjOST4m3 5TpWJAUbArzp6OQYypmqaUCYapY1F0YPcJzwrUZx5MiSEuwNSig3j3YwYEu7Q1BY qNPgfPYQfpGxVFZwbF46C6TXgmsCsf1Kl5s/41bMjXDyE0nB2fWER75AH5sV1weM uD9EUkZDyJmCEFcdjvm3La3q3VI8FiX5FMD/JdMyc1Sg2jl092IRvfVjIdhv/XgA r5Nb9IXrY7CNyA+plG1/MlBahCV+RpeZZkLvzE/d9BUekC3MEyBg1St4+czP2qsU Anu8bNMySJyv8OrHDPByw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdejuddgudelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuhffvfhgjtgfgsehtke ertddtfeejnecuhfhrohhmpefrvghtvghrucfgihhsvghnthhrrghuthcuoehpvghtvghr rdgvihhsvghnthhrrghuthesvghnthgvrhhprhhishgvuggsrdgtohhmqeenucggtffrrg htthgvrhhnpeefgefgteefudehheduffevlefhkeeulefhfffgvdelgfffueduledtgfek iefhjeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe hpvghtvghrrdgvihhsvghnthhrrghuthesvghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Feedback-ID: i131946ab:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Wed, 5 Apr 2023 05:41:48 -0400 (EDT) Message-ID: Date: Wed, 5 Apr 2023 11:41:47 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.9.1 Subject: Re: documentation updates for SQL:2023 Content-Language: en-US From: Peter Eisentraut To: pgsql-hackers References: <63f285d9-4ec8-0c9e-4bf5-e76334ddc0af@enterprisedb.com> In-Reply-To: <63f285d9-4ec8-0c9e-4bf5-e76334ddc0af@enterprisedb.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 01.03.23 10:12, Peter Eisentraut wrote: > SQL:2023 should be published within the next 2 months, so I want to > update our SQL conformance information for our PostgreSQL release later > this year. > > Attached are patches that update the keywords list and the features list > as usual.  (Some of the new features in the JSON area are still being > worked on.  I have just set them all to NO for now, to be revisited later.) I have committed these patches. > I'm also proposing to get rid of the tracking of subfeatures.  This has > been de-facto deprecated: All the subfeatures for optional features have > been removed (replaced by top-level feature codes), and the subfeatures > for mandatory features aren't very interesting.  The TODO is to remove > the columns for the subfeatures in src/backend/catalog/sql_features.txt. >  That is a mechanical change that I did not include in the patch. I have dropped this for now. This got a little bit more complicated than I had hoped, since the sql_features.txt file is also loaded into the information schema in initdb, and I didn't want to reorganize that right now. Something to revisit some other time, perhaps.