Re: anyelement -> anyrange - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: anyelement -> anyrange
Date
Msg-id CAKFQuwYWN3M7fv5ukV_LidpAqM6EgO9gaSVsvdmRsov3-Tpfkw@mail.gmail.com
Whole thread Raw
In response to Re: anyelement -> anyrange  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: anyelement -> anyrange  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
On Tue, Aug 16, 2016 at 7:47 PM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
On 8/15/16 10:12 PM, Tom Lane wrote:
Jim Nasby <Jim.Nasby@BlueTreble.com> writes:
Any reason why we can create a function that accepts anyelement and
returns anyarray, but can't do the same with anyrange?

Because there can be more than one range type over the same element
type, so we couldn't deduce which one should be used for anyrange.

The other direction (inferring anyelement from anyrange) does work.

Is there an actual use case for that? I'm not seeing what it would be...


lower() and upper() both use it.

David J.
 

pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: anyelement -> anyrange
Next
From: Jim Nasby
Date:
Subject: Re: [Patch] Temporary tables that do not bloat pg_catalog (a.k.a fast temp tables)