Re: Greatest Common Divisor
От | Robert Haas |
---|---|
Тема | Re: Greatest Common Divisor |
Дата | |
Msg-id | CA+TgmoaF6+PJiOGSqr63Dh_5fDN6_wrucR8N8=CL_VqpB=DSuA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Greatest Common Divisor (Chapman Flack <chap@anastigmatix.net>) |
Ответы |
Re: Greatest Common Divisor
|
Список | pgsql-hackers |
On Fri, Jan 3, 2020 at 2:27 PM Chapman Flack <chap@anastigmatix.net> wrote: > On 1/3/20 2:11 PM, Robert Haas wrote: > > and moving things to another schema does not help with that. It does > > potentially help with the namespace pollution issue, but how much of > > an issue is that anyway? Unless you've set up an unusual search_path > > configuration, your own schemas probably precede pg_catalog in your > > search path, besides which it seems unlikely that many people have a > > gcd() function that does anything other than take the greatest common > > divisor. > > As seen in this thread though, there can be edge cases of "take the > greatest common divisor" that might not be identically treated in a > thoroughly-reviewed addition to core as in someone's hastily-rolled > local version. True, but because of the way search_path is typically set, they'd probably continue to get their own version anyway, so I'm not sure what the problem is. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: