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 1s00hZ-008qQo-Hr for pgsql-hackers@arkaria.postgresql.org; Thu, 25 Apr 2024 15:07:57 +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 1s00hX-007vQ4-R7 for pgsql-hackers@arkaria.postgresql.org; Thu, 25 Apr 2024 15:07:55 +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.94.2) (envelope-from ) id 1s00hX-007vPw-Hb for pgsql-hackers@lists.postgresql.org; Thu, 25 Apr 2024 15:07:55 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s00hQ-004bNq-QD for pgsql-hackers@postgresql.org; Thu, 25 Apr 2024 15:07:54 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 43PF7kmT3936414; Thu, 25 Apr 2024 11:07:46 -0400 From: Tom Lane To: jian he cc: Yugo NAGATA , PostgreSQL-development Subject: Re: minor error message inconsistency in make_pathkey_from_sortinfo In-reply-to: References: <20240424184736.d16803a87d6c8a22088e0a2b@sraoss.co.jp> Comments: In-reply-to jian he message dated "Thu, 25 Apr 2024 22:52:14 +0800" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <3936412.1714057666.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Thu, 25 Apr 2024 11:07:46 -0400 Message-ID: <3936413.1714057666@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk jian he writes: > On Wed, Apr 24, 2024 at 5:47 PM Yugo NAGATA wrote: >> This message was introduced by 278cb434110 which was aiming to >> standardize the wording for similar errors. We can find the pattern >> "missing {support function | operator} %d(%u,%u) in opfamily %u" >> in several places. > the error message > ` operator %d` > would translate to > ` operator 3` > but there is oid as 3 operator in the catalog. > that's my confusion. That number is the opclass' operator strategy number, not an OID (which is why it's formatted as %d not %u). See https://www.postgresql.org/docs/devel/xindex.html#XINDEX-STRATEGIES regards, tom lane