Re: Improve upcasting for INT range and multi range types - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Improve upcasting for INT range and multi range types
Date
Msg-id 2529538.1702440987@sss.pgh.pa.us
Whole thread Raw
In response to Re: Improve upcasting for INT range and multi range types  (jian he <jian.universality@gmail.com>)
Responses Re: Improve upcasting for INT range and multi range types
List pgsql-hackers
jian he <jian.universality@gmail.com> writes:
> Based on my interpretation, I don't think SELECT 2::INT4 <@ '[1,
> 4)'::INT8RANGE is doable.

Yeah, it would require a considerable expansion of the scope of
what can be matched by a polymorphic operator.  I'm afraid that
the negative consequences (mainly, "ambiguous operator" failures
because more than one thing can be matched) would outweigh the
benefits.  It is kind of annoying though that the system can't
do the "obvious" right thing here.

            regards, tom lane



pgsql-hackers by date:

Previous
From: jian he
Date:
Subject: Re: Improve upcasting for INT range and multi range types
Next
From: Dilip Kumar
Date:
Subject: Re: SLRU optimization - configurable buffer pool and partitioning the SLRU lock