| From: | "Joel Jacobson" <joel(at)compiler(dot)org> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Mark Dilger" <mark(dot)dilger(at)enterprisedb(dot)com> |
| Cc: | "Postgres hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "Isaac Morland" <isaac(dot)morland(at)gmail(dot)com>, "Jeff Davis" <pgsql(at)j-davis(dot)com> |
| Subject: | Re: [PATCH] Support empty ranges with bounds information |
| Date: | 2021-03-02 20:26:50 |
| Message-ID: | 07871142-ef8a-401b-a7e2-7bb9ab16cf15@www.fastmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 2, 2021, at 19:28, Tom Lane wrote:
> More generally, values that are visibly different yet compare equal
> are user-unfriendly in the extreme. We do have cases like that
> (IEEE-float minus zero, area-based compare of some geometric types
> come to mind) but they are all warts, not things to be emulated.
I almost agree with you, but if forced to choose,
I would rather have two wart feet I can use, rather than limping around on only one wart free foot.
/Joel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2021-03-02 20:39:29 | Re: new heapcheck contrib module |
| Previous Message | Justin Pryzby | 2021-03-02 20:26:17 | Re: [PATCH] Automatic HASH and LIST partition creation |