Re: empty range - Mailing list pgsql-hackers

From Emre Hasegeli
Subject Re: empty range
Date
Msg-id CAE2gYzxxtfCt3oP=bMsgRQPSVO6yYwNgPGhXf-ctJWdDFGFzHA@mail.gmail.com
Whole thread Raw
In response to empty range  (david.turon@linuxbox.cz)
Responses Re: empty range  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> 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 eliminate
special cases on most of the range operators.  For reference, we allow
empty boxes, and none of the geometric operators has to handle them
specially.



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: SlabCheck leaks memory into TopMemoryContext
Next
From: Georgios Kokolatos
Date:
Subject: Re: Duplicate Workers entries in some EXPLAIN plans