| From: | Pantelis Theodosiou <ypercube(at)gmail(dot)com> |
|---|---|
| To: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
| Cc: | Joel Jacobson <joel(at)compiler(dot)org>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
| Subject: | Re: [PATCH] Support empty ranges with bounds information |
| Date: | 2021-03-02 16:51:01 |
| Message-ID: | CAE3TBxxKOsdOCRka+652gfS12JUQDqa5y-D6vWz6H3-vsx7GQA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 2, 2021 at 3:28 PM Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>
wrote:
>
>
> > On Mar 2, 2021, at 5:20 AM, Joel Jacobson <joel(at)compiler(dot)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/4D5534D0020000250003A87E@gw.wicourts.gov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vik Fearing | 2021-03-02 16:51:52 | Re: GROUP BY DISTINCT |
| Previous Message | Bruce Momjian | 2021-03-02 16:40:21 | GiST comment improvement |