152
www.linuxbox.cz
mobil servis: +420 737 238 656
email servis: ser...@linuxbox.cz
-
Od: "Tom Lane"
Komu: e...@hasegeli.com
Kopie: david.tu...@linuxbox.cz, pgsql-hack...@postgresql.org
Datum: 16. 01. 2020 16:21
Předmět:Re: em
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
> keepi
> 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 flexibilit
unds in internal structure 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
tstzrang
