| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Chapman Flack <chap(at)anastigmatix(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Greatest Common Divisor |
| Date: | 2020-01-03 20:09:38 |
| Message-ID: | cb704408-6589-00a3-3dc5-4dcb08d94819@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-01-03 16:22, Tom Lane wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
>> On 2020-01-02 15:50, Dean Rasheed wrote:
>>> Out of curiosity, what was the original use-case for this?
>
>> Yeah, I'm wondering, is this useful for any typical analytics or
>> business application? Otherwise, abstract algebra functionality seems a
>> bit out of scope.
>
> Nobody complained when we added sinh, cosh, tanh, asinh, acosh, atanh
> last year, so I'm feeling skeptical of claims that gcd should be out
> of scope.
Geometry is generally in scope, though, for Postgres specifically and
for databases in general.
Abstract algebra is not in scope, so far, and we still haven't been told
the use case for this.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2020-01-03 20:25:47 | Re: color by default |
| Previous Message | Robbie Harwood | 2020-01-03 20:01:25 | Re: weird libpq GSSAPI comment |