Horton

Re: Greatest Common Divisor

Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Dean Rasheed <dean.a.rasheed@gmail.com>, Vik Fearing <vik.fearing@2ndquadrant.com>, Fabien COELHO <coelho@cri.ensmp.fr>, Chapman Flack <chap@anastigmatix.net>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-01-03T20:09:38Z
Lists: pgsql-hackers 
On 2020-01-03 16:22, Tom Lane wrote:
> Peter Eisentraut <peter.eisentraut@2ndquadrant.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

Commits

  1. Add functions gcd() and lcm() for integer and numeric types.