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 1rdW5R-005zsa-BX for pgsql-docs@arkaria.postgresql.org; Fri, 23 Feb 2024 13:59:38 +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 1rdW5P-001HVM-U8 for pgsql-docs@arkaria.postgresql.org; Fri, 23 Feb 2024 13:59:36 +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 1rdW5O-001HV1-2S for pgsql-docs@lists.postgresql.org; Fri, 23 Feb 2024 13:59:36 +0000 Received: from wfhigh6-smtp.messagingengine.com ([64.147.123.157]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rdW5K-000WjU-5F for pgsql-docs@lists.postgresql.org; Fri, 23 Feb 2024 13:59:33 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailfhigh.west.internal (Postfix) with ESMTP id 162471800078; Fri, 23 Feb 2024 08:59:26 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Fri, 23 Feb 2024 08:59:27 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eisentraut.org; h=cc:cc:content-transfer-encoding:content-type:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:subject:subject:to:to; s=fm3; t=1708696766; x=1708783166; bh=twItmuHoQUebZRMHgPEPF0O9najhoOJ/ lJGEraYGPPk=; b=Hxc4N7ZI1fHNqhutTBHiabmrVioclklIlgOZYe5BiZFBVKcZ /a7ryecjT+0n1oG4ci2U/il0TgpRbdNgtH+NAB9LigzF99lx8Nn6JgmirM/VxrpZ ku8ca9eyLSaE+TiY6klwgYv5JDfeasQW6DfXg97eXrmnQU+7jtlvVmkMt7ds1M2f wV6vIHSJnVWdqRzBKzrhUUdlRL+FjX2MV+IaNixU+BxHd2G0s+CvrFL7FpQiTjCY 7BpRf95G1jBnYSr3fOAofbnfQf7+2VXkFvxdWGlZpnqKsttKs5KYNcFft8Re6ym/ gcsamvPMmCVCGzZL8aXcLSbR9dFBIZplda+edw== 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 :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1708696766; x= 1708783166; bh=twItmuHoQUebZRMHgPEPF0O9najhoOJ/lJGEraYGPPk=; b=l PdmyoOnVJeXHLYHvRM6SlAUIjVYvg1PDakDB9bbEAxcvjCNF+FeMb15drKnk+Pdy oQKYtrTf50IhT4UJ0ODsEF/6aMmsMkfA204Xhl3LfI737DVPKvBXyEFGipmP4L07 u4+/xqGSBr9yLaXGGmDzbLvCuM3OllIUMvFYuz3g90muERxVThVE6ZypSlQrXFKw JBGa5mBrwbJUz1fDdn8tojqhAjxBQ7qw5nMvzcYojNfoyRVUFNvzVx/YEqAu7YdS qnZIB1EgKPID8ZhTgNtUTr3BxZiqQShGSciNaesqZ53iwH3KoCHdC3jaHVvLyrC5 rCvVl4kpDhhOnOWeCTmJQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrfeeigdehlecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfevfhfhjggtgfesthekredttddvjeenucfhrhhomheprfgvthgv rhcugfhishgvnhhtrhgruhhtuceophgvthgvrhesvghishgvnhhtrhgruhhtrdhorhhgqe enucggtffrrghtthgvrhhnpeejhfevhedttefgfffhhfeffefggffhffelgfeiueeukeeh vdehvdefheffvdefueenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehpvghtvghrsegvihhsvghnthhrrghuthdrohhrgh X-ME-Proxy: Feedback-ID: ie0a040ee:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 23 Feb 2024 08:59:25 -0500 (EST) Message-ID: Date: Fri, 23 Feb 2024 14:59:23 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual Content-Language: en-US To: =?UTF-8?B?5bCP5rOJIOaCnw==?= , Daniel Gustafsson Cc: pgsql-docs References: <170866661469.645.14101429540172934386@wrigleys.postgresql.org> <98185277-F389-4B32-B0EB-D1D2DF52A8D0@yesql.se> From: Peter Eisentraut In-Reply-To: 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 23.02.24 12:23, 小泉 悟 wrote: > Upon closer inspection, F305 is also "INTERSECT ALL table operator”. > Perhaps F302-02 would be unnecessary. Correct, F302-02 should have been deleted. I have fixed it, thanks. > >> 2024/02/23 18:06、Daniel Gustafsson のメール: >> >>> On 23 Feb 2024, at 06:36, PG Doc comments form wrote: >> >>> The correct result would be as follows: >>> >>> F302 INTERSECT table operator >>> F302-02 INTERSECT ALL table operator >>> F303 INTERSECT DISTINCT table operator >>> F304 EXCEPT ALL table operator >> >> This was changed recently in c9f57541d970 which changed subfeatures to >> top-level features to match the SQL:2023 standard, F303 was previously a >> sub-feature named F302-01. That being said, I agree that it makes sense to >> place F303 below F302-02 as per the attached, unless Peter (on cc:) objects. >> >> -- >> Daniel Gustafsson >> >> > > >