| From: | Emre Hasegeli <emre(at)hasegeli(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Improve geometric types |
| Date: | 2017-10-04 16:42:03 |
| Message-ID: | CAE2gYzzn=NYsKs-6UOrjjxi1yFR0=S1qOK43D5dPOtiPVKPdEw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Now, it's also not clear that anything in PG really cares. But if we
> do care, I think we should keep pg_hypot() ... and maybe clarify the
> comment a bit more.
I am not sure how useful NaNs are in geometric types context, but we
allow them, so inconsistent hypot() would be a problem. I will change
my patches to keep pg_hypot().
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-10-04 16:57:27 | Re: Horrible CREATE DATABASE Performance in High Sierra |
| Previous Message | Brent Dearth | 2017-10-04 16:41:53 | Re: Horrible CREATE DATABASE Performance in High Sierra |