| From: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
|---|---|
| To: | Joel Jacobson <joel(at)compiler(dot)org> |
| Cc: | 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 15:28:05 |
| Message-ID: | 7CFEE5E4-BFB3-4C90-8151-0BDE453C68B0@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dilip Kumar | 2021-03-02 15:31:41 | Re: [Patch] ALTER SYSTEM READ ONLY |
| Previous Message | Tom Lane | 2021-03-02 15:23:09 | Re: psql crash while executing core regression tests |