Re: BUG #17066: Cache lookup failed when null (iso-8859-1) is passed as anycompatiblemultirange - Mailing list pgsql-bugs

From Alexander Korotkov
Subject Re: BUG #17066: Cache lookup failed when null (iso-8859-1) is passed as anycompatiblemultirange
Date
Msg-id CAPpHfdtd210xzVVBQnhEuXk0_UCLCumA02beF0tqvLbm80TbLw@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17066: Cache lookup failed when null (iso-8859-1) is passed as anycompatiblemultirange  (Alexander Lakhin <exclusion@gmail.com>)
Responses Re: BUG #17066: Cache lookup failed when null (iso-8859-1) is passed as anycompatiblemultirange  (Alexander Korotkov <aekorotkov@gmail.com>)
List pgsql-bugs
On Fri, Jun 25, 2021 at 7:00 AM Alexander Lakhin <exclusion@gmail.com> wrote:
> Hello,
> 24.06.2021 02:35, Tom Lane wrote:
> > Alexander Korotkov <aekorotkov@gmail.com> writes:
> >> I really appreciate a hint here.
> > I think I'm to blame for most of that code originally, so I'll take
> > a look soon.  Been up to my neck in other stuff recently.
> I'm not sure whether it related to the initial issue, but there is
> another anomaly with the multirange types. (May be I should report it as
> a distinct bug?) The query:
> create table test_multirange(mr int4multirange);
> select count(*) from test_multirange where mr << int4range(100,100);
> produces:
> ERROR:  unexpected operator 4396
>
> while
> select count(*) from test_multirange where mr << int4range(100,500);
> returns a result (as the multirangetypes test shows).

Yep, that's a distinct bug.  It seems that I've added some missing
operators, but forgot to add some selectivity estimates for them.

I'll come with a fix soon.

------
Regards,
Alexander Korotkov



pgsql-bugs by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: IRe: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows
Next
From: Amit Kapila
Date:
Subject: Re: BUG #17072: Assert for clogGroupNext failed due to a race condition in TransactionGroupUpdateXidStatus()