Emre Hasegeli writes:
>> It's only suggestion, i don't now if somebody wants store empty range
>> without bounds.
> I thought about the same while developing the BRIN inclusion operator
> class. I am not sure how useful empty ranges are in practice, but
> keeping their b
> It's only suggestion, i don't now if somebody wants store empty range without
> bounds.
I thought about the same while developing the BRIN inclusion operator
class. I am not sure how useful empty ranges are in practice, but
keeping their bound would only bring more flexibility, and eli
and lower(tstzrange(now(),now())) show
not NULL value or change default behavior
tstzrange(timestamptz,timestamptz) - if both args are same, then store as
'[]', else '[)' and only tstzrange(timestamptz,timestamtz,'[)') and
tstzrange(timestamptz,timestamtz,'()') store empty range.
It's only
