Re: minor error message inconsistency in make_pathkey_from_sortinfo - Mailing list pgsql-hackers

From Yugo NAGATA
Subject Re: minor error message inconsistency in make_pathkey_from_sortinfo
Date
Msg-id 20240424184736.d16803a87d6c8a22088e0a2b@sraoss.co.jp
Whole thread Raw
In response to minor error message inconsistency in make_pathkey_from_sortinfo  (jian he <jian.universality@gmail.com>)
Responses Re: minor error message inconsistency in make_pathkey_from_sortinfo
List pgsql-hackers
On Wed, 24 Apr 2024 15:05:00 +0800
jian he <jian.universality@gmail.com> wrote:

> hi.
> 
> in make_pathkey_from_sortinfo
> 
> equality_op = get_opfamily_member(opfamily,
>   opcintype,
>   opcintype,
>   BTEqualStrategyNumber);
> if (!OidIsValid(equality_op)) /* shouldn't happen */
> elog(ERROR, "missing operator %d(%u,%u) in opfamily %u",
> BTEqualStrategyNumber, opcintype, opcintype, opfamily);
> 
> the error message seems not right?

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.

Regards,
Yugo Nagata

> 
> maybe
> if (!OidIsValid(equality_op)) /* shouldn't happen */
> elog(ERROR, "missing operator =(%u,%u) in opfamily %u",opcintype,
> opcintype, opfamily);
> 
> or
> 
> if (!OidIsValid(equality_op)) /* shouldn't happen */
> elog(ERROR, "missing equality operator for type %u in opfamily
> %u",opcintype, opcintype, opfamily);
> 
> 


-- 
Yugo NAGATA <nagata@sraoss.co.jp>



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Q: Escapes in jsonpath Idents
Next
From: Matthias van de Meent
Date:
Subject: Re: Cleanup: remove unused fields from nodes