Re: Modifying and solidifying contrib

>> Well to me that gets a little messy. I mean:
>>
>> pg_catalog,public,<user schemas>,xml2,ltree (just to get a could
>> functions?) etc...
> 
> Not as messy as trying to drop or re-create a package when there are
> already 500 functions in the public schema.

I am not sure I understand the correlation. I am not suggesting we
install anything into public. They would all go into a single additional
schema called extensions or some such.

>>>> Obviously the initdb switch could also be selective:
>>>>
>>>> initdb --enable-extensions
>>> If it were an initdb switch, I'd want to have something more like
>>>
>>> --enable-extension=earthdistance
>> And have to parse for each extension?
> 
> I don't see this as a big problem.

Well I am not really interesting in this. Someone else is welcome to try
that.

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/