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.96) (envelope-from ) id 1vfJku-000vms-0N for pgsql-docs@arkaria.postgresql.org; Mon, 12 Jan 2026 15:22:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vfJks-000sPD-1a for pgsql-docs@arkaria.postgresql.org; Mon, 12 Jan 2026 15:22:54 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vfHO2-000UVR-1J for pgsql-docs@lists.postgresql.org; Mon, 12 Jan 2026 12:51:10 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vfHNw-0001Rz-2Q for pgsql-docs@lists.postgresql.org; Mon, 12 Jan 2026 12:51:09 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=w5e0uqfTxe95xAuQ14j8nZ2aBEbFPh5guK10zORYsew=; b=pWOBEhNVmIfAYfEA8+vshq2ATs w6/YZdZOhF/8hvAB/GdJ1Eadtc1MB+xtmu4m/TYKQAiQ4JgMTaCki2jefIlRrWsW/Hy/TRG/daa93 3o/eo1J1cSSmEETZYwz+66OLsIBpGheXFqy4vn6HX8PxoVqUqv/jobKr06fRWiFx8FW2TwY+hDH/L p8IPTxml0mVkg1De3RRURvUDyoMKBajzB98iBHsWI9ICDYH3CgOqtflvQJLd2r0fbxCmcIbsCyIuT /h5xiw+C3ywnMx20lsI39btLtb9OW8cXNIidrJw3st1twC75Y4esgftHK7BqvgbWj/ZQLCo0Wb3LB RK02SkNw==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vfHNw-000EO8-08 for pgsql-docs@lists.postgresql.org; Mon, 12 Jan 2026 12:51:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vfHNu-0009sr-2O for pgsql-docs@lists.postgresql.org; Mon, 12 Jan 2026 12:51:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: Exact number of mandatory features required for full Core conformance in SQL:2023 To: pgsql-docs@lists.postgresql.org From: PG Doc comments form Cc: jackietien97@gmail.com Reply-To: jackietien97@gmail.com, pgsql-docs@lists.postgresql.org Date: Mon, 12 Jan 2026 12:50:12 +0000 Message-ID: <176822221254.769.2631427545452619968@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/18/features.html Description: I read the ISO IEC 9075-2 2023 and ISO IEC 9075-11 2023, I found that there are 163 features listed in Table H.1 of ISO IEC 9075-2 2023 and 15 features listed in Table H.1 of ISO IEC 9075-11 2023. So should the number be 178 instead of the 177 ?