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

From Jim Nasby
Subject Re: Freeze avoidance of very large table.
Date
Msg-id 55C37E40.6080700@BlueTreble.com
Whole thread Raw
In response to Re: Freeze avoidance of very large table.  (Petr Jelinek <petr@2ndquadrant.com>)
Responses Re: Freeze avoidance of very large table.  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 8/5/15 1:47 PM, Petr Jelinek wrote:
> 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).

They also provide a level of control over what is and isn't installed in 
a cluster. Personally, I'd prefer that most users not even be aware of 
the existence of things like pageinspect.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Data in Trouble? Get it in Treble! http://BlueTreble.com



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: deparsing utility commands
Next
From: Andres Freund
Date:
Subject: Re: Raising our compiler requirements for 9.6