On Tue, Mar 2, 2021 at 3:28 PM Mark Dilger <mark.dil...@enterprisedb.com> wrote:
> > > > On Mar 2, 2021, at 5:20 AM, Joel Jacobson <j...@compiler.org> wrote: > > > > it's currently not possible to create an empty range with bounds > information. > > > > This patch tries to improve the situation by keeping the bounds > information, > > and allow accessing it via lower() and upper(). > > > > No other semantics have been changed. > > All tests passes without any changes. > > I recall this issue of empty ranges not keeping any bounds information > being discussed back when range types were developed, and the design choice > was intentional. Searching the archives for that discussion, I don't find > anything, probably because I'm not searching for the right keywords. > Anybody have a link to that discussion? > > — > Mark Dilger > EnterpriseDB: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > > Marc, perhaps you were referring to this discussion? https://www.postgresql.org/message-id/4d5534d0020000250003a...@gw.wicourts.gov
