Re: Greatest Common Divisor - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Greatest Common Divisor
Date
Msg-id CA+TgmoYf5HtD5f5nA5=0Pf7HSUSivx4UkhsdR1tf=a2YJLBaFQ@mail.gmail.com
Whole thread Raw
In response to Re: Greatest Common Divisor  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Greatest Common Divisor  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Fri, Jan 3, 2020 at 4:11 PM Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
> Maybe a very simple solution is indeed to have a separate pg_math or
> pg_extra or whatever, which by default is *last* in the search_path.
> That would make a user's gcd() be chosen preferently, if one exists.

Then every time we add a function, or anything else, we can bikeshed
about whether it should go in pg_catalog or pg_extra!

FWIW, EnterpriseDB has something like this for Advanced Server, and it
actually adds a fair amount of complexity, much of it around
OverrideSearchPath. It's not unmanageable, but it's not trivial,
either.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Greatest Common Divisor
Next
From: Alvaro Herrera
Date:
Subject: Re: Greatest Common Divisor