Re: BUG #13608: 3 argument range constructor functions - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #13608: 3 argument range constructor functions
Date
Msg-id 21535.1441236549@sss.pgh.pa.us
Whole thread Raw
In response to BUG #13608: 3 argument range constructor functions  (robert.kruus@gov.sk.ca)
List pgsql-bugs
robert.kruus@gov.sk.ca writes:
> The int4range, int8range, daterange functions seem to be ignoring the 3rd
> argument which specifies the interval bounds.
> i.e.
> SELECT daterange('2010-01-01'::date, '2011-01-01'::date, '()'::text);
>         daterange
> -------------------------
>  [2010-01-02,2011-01-02)

It's not ignoring it.  What it's doing is canonicalizing the range so that
equivalent ranges actually look the same.  Note your bounds have changed.
(BTW, you misquoted the result; the upper date does not change in this
case, at least not for me.)

See the discussion of discrete vs continuous range types at

http://www.postgresql.org/docs/9.3/static/rangetypes.html#RANGETYPES-DISCRETE

            regards, tom lane

pgsql-bugs by date:

Previous
From: Andres Freund
Date:
Subject: Re: BUG #13440: unaccent does not remove all diacritics
Next
From: Tom Lane
Date:
Subject: Re: BUG #13440: unaccent does not remove all diacritics