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

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

On Thu, May 13, 2021 at 02:22:16PM -0400, Tom Lane wrote:
> 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?

Sure, no problem. I'm just passing on the message :)

--
Justin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-05-13 18:29:09 Re: compute_query_id and pg_stat_statements
Previous Message Tom Lane 2021-05-13 18:22:16 Re: amvalidate(): cache lookup failed for operator class 123