Re: Modifying and solidifying contrib - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: Modifying and solidifying contrib
Date
Msg-id 45BC3965.5050504@commandprompt.com
Whole thread Raw
In response to Re: Modifying and solidifying contrib  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Modifying and solidifying contrib  (David Fetter <david@fetter.org>)
Re: Modifying and solidifying contrib  ("Kevin Barnard" <kevin.barnard@gmail.com>)
Re: Modifying and solidifying contrib  (Richard Huxton <dev@archonet.com>)
List pgsql-hackers
Tom Lane wrote:
> "Joshua D. Drake" <jd@commandprompt.com> writes:
>> So what are we thinking here? Along with my suggestion of extensions /
>> contrib that we modify initdb to load an extensions schema with all
>> extensions into template1?
> 
> No, I don't think so.  If you do that it's effectively moving all that
> stuff into core, especially if you haven't provided a way to turn it off.

O.k. any thoughts there? What if we didn't make the extensions schema
PUBLIC? Meaning that explicits rights would have to be given for the
extensions to be used by anyone but a super user?

Obviously the initdb switch could also be selective:

initdb --enable-extensions

?

Sincerely,

Joshua D. Drake



-- 
     === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997            http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Modifying and solidifying contrib
Next
From: David Fetter
Date:
Subject: Re: Modifying and solidifying contrib