> No, that's the point of the sentence about the range mechanisms not
> understanding special values of the underlying type. upper_inf tests
> for a range with no upper bound, period. It would need some
> type-specific special knowledge to do what you're hoping for, and it
> has not got that.
Go
Ralph Graulich writes:
> select upper_inf(tsrange('2013-05-01'::timestamp, 'infinity'::timestamp,
> '[]'));
> upper_inf
> ---
> f
> (1 row)
> As far as I understood the docs, this query should return true, as the upper
> bound includes 'infinity'?
No, that's the point of the sentenc
Hi,
> select upper_inf(tsrange('2013-05-01'::timestamp, 'infinity'::timestamp,
> '[]'));
upper_inf
---
f
(1 row)
As far as I understood the docs, this query should return true, as the upper
bound includes 'infinity'?
[http://www.postgresql.org/docs/9.2/interactive/functions-range.ht
