Re: Additional supplied modules

From: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Additional supplied modules
Date: 2011-10-13 18:46:21
Message-ID: m2hb3cbugy.fsf@2ndQuadrant.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Josh Berkus <josh(at)agliodbs(dot)com> writes:
> On 10/13/11 6:32 AM, Thom Brown wrote:
>> Could we somehow categorise these, and also do something to clarify
>> that SPI is a collection of extensions rather than an extension
>> itself?
>
> Alternately we should clean up SPI and break it out into its separate
> extensions.

Additionaly we need to pick some and bless them as in-core extensions
(installed by default, you still need to CREATE EXTENSION to benefit
from them) and move the others into either an "example" section or an
"additional" section where production ready goodies are to be found but
just were not selected as in-core extensions for whatever reasons
(export laws in the case of pgcrypto, some non portable dependencies for
other choices, etc).

We might even have some more categories into, such as "debug",
"profile", "data type", "compat" and all. Maybe a new field with that
kind of classification in the control file would be good (it would be
found in the catalogs too).

Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thom Brown 2011-10-13 19:12:01 Re: Additional supplied modules
Previous Message David E. Wheeler 2011-10-13 18:29:03 Re: pl/perl example in the doc no longer works in 9.1