Re: Freeze avoidance of very large table. - Mailing list pgsql-hackers

From Petr Jelinek
Subject Re: Freeze avoidance of very large table.
Date
Msg-id 55C25A41.9050702@2ndquadrant.com
Whole thread Raw
In response to Re: Freeze avoidance of very large table.  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Freeze avoidance of very large table.  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
On 2015-08-05 20:09, Alvaro Herrera wrote:
> Josh Berkus wrote:
>> On 08/05/2015 10:46 AM, Alvaro Herrera wrote:
>>> 1. Add the functions as a builtins.
>>>     This is what the current patch does.  Simon seems to prefer this,
>>>     because he wants the function to be always available in production;
>>>     but I don't like this option because adding functions as builtins
>>>     makes it impossible to move later to extensions.
>>>     Bruce doesn't like this option either.
>>
>> Why would we want to move them later to extensions?
>
> Because it's not nice to have random stuff as builtins.
>

Extensions have one nice property, they provide namespacing so not 
everything has to be in pg_catalog which already has about gazilion 
functions. It's nice to have stuff you don't need for day to day 
operations separate but still available (which is why src/extensions is 
better than contrib).

--  Petr Jelinek                  http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [sqlsmith] Failed assertion in joinrels.c
Next
From: Andreas Seltenreich
Date:
Subject: Re: [sqlsmith] Failed assertion in joinrels.c