Re: anyelement -> anyrange

Jim Nasby <Jim.Nasby@bluetreble.com> writes:
> I can't think of any reason you'd want two different range types on a 
> single element type.

We would not have built it that way if there were not clear use-cases.
An easy example is you might want both a continuous timestamp range
and one that is quantized to hour boundaries.  Primarily what the
range type brings in besides the element type is a canonicalization
function; and we can't guess which one you want.
        regards, tom lane