Re: amvalidate(): cache lookup failed for operator class 123

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: amvalidate(): cache lookup failed for operator class 123
Date: 2021-05-13 18:22:16
Message-ID: 1579224.1620930136@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Justin Pryzby <pryzby(at)telsasoft(dot)com> writes:
> Per sqlsmith.
> postgres=# select amvalidate(123);
> ERROR: cache lookup failed for operator class 123
> postgres=# \errverbose
> ERROR: XX000: cache lookup failed for operator class 123
> LOCATION: amvalidate, amapi.c:125

> The usual expectation is that sql callable functions should return null rather
> than hitting elog().

Meh. I'm not convinced that that position ought to apply to amvalidate.
Under what circumstances would you be calling that on an opclass that
might be about to be dropped?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2021-05-13 18:28:17 Re: amvalidate(): cache lookup failed for operator class 123
Previous Message Stephen Frost 2021-05-13 18:07:06 Re: compute_query_id and pg_stat_statements