| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Infinities in type numeric |
| Date: | 2020-07-21 22:18:26 |
| Message-ID: | 1199108.1595369906@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> writes:
>> I had a look at this, and I think it's mostly in good shape. It looks
>> like everything from the first message in this thread has been
>> resolved, except I don't know about the jsonpath stuff, because I
>> haven't been following that.
> Thanks for the careful review!
Here's a v4 that syncs numeric in_range() with the new behavior of
float in_range(), and addresses your other comments too.
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| numeric-infinities-4.patch | text/x-diff | 124.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-07-21 22:25:00 | Re: v13 planner ERROR: could not determine which collation to use for string comparison |
| Previous Message | Peter Geoghegan | 2020-07-21 21:52:21 | Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held) |