BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: exclusion(at)gmail(dot)com
Subject: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange
Date: 2021-06-20 21:00:01
Message-ID: 17066-16a37f6223a8470b@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 17066
Logged by: Alexander Lakhin
Email address: exclusion(at)gmail(dot)com
PostgreSQL version: 14beta1
Operating system: Ubuntu 20.04
Description:

When calling the simple test function:
create function multirange_test(a anycompatiblemultirange)
returns anycompatible as 'select lower($1);' language sql;

with the NULL argument:
SELECT multirange_test(null);

I get a somewhat unusual error:
ERROR: cache lookup failed for type 0

The variation with the anycompatiblerange (without multi):
create function range_test(a anycompatiblerange)
returns anycompatible as 'select lower($1);' language sql;
SELECT range_test(null);

produces:
ERROR: could not determine polymorphic type anycompatiblerange because
input has type unknown

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2021-06-21 03:11:16 BUG #17067: FailedAssertion at castNodeImpl
Previous Message Tom Lane 2021-06-20 20:15:08 Re: BUG #17062: Assert failed in RemoveRoleFromObjectPolicy() on DROP OWNED policy applied to duplicate role