| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | jian he <jian(dot)universality(at)gmail(dot)com> |
| Cc: | Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: minor error message inconsistency in make_pathkey_from_sortinfo |
| Date: | 2024-04-25 15:07:46 |
| Message-ID: | 3936413.1714057666@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
jian he <jian(dot)universality(at)gmail(dot)com> writes:
> On Wed, Apr 24, 2024 at 5:47 PM Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2024-04-25 15:30:58 | Re: New GUC autovacuum_max_threshold ? |
| Previous Message | Andres Freund | 2024-04-25 15:05:37 | Re: AIX support |