Re: plPHP and plRuby - Mailing list pgsql-hackers

From Marcin Mank
Subject Re: plPHP and plRuby
Date
Msg-id 009401c6b006$9bdc0d60$0c67a8c0@maniek
Whole thread Raw
In response to plPHP and plRuby  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
> Ultimately, I really think we need something akin to CPAN so that we
> don't have to bundle all kinds of stuff in the core package. In the
> meantime, adding PLs that we can is better than not, but we do need to
> be mindful of the impression it might leave on users. A page that lists
> the status of all PLs (specifically why they're not included if they're
> not) would be a good thing to have.

I as a user think that there should be a clear distinction of what is a
supported extension, and what is an unsupported extension .

With >100 projects on pgfoundry, 150 or so on gborg, it is hard to tell
which ones one can trust, and not everybody wants to beta-test on their
production data (especially for things that touch the core engine directly).
Maybe there should be a set of requirements fulfilling of which could get a
project a special 'blessing' from the Postgresql community?

Greetings
Marcin Mank



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: root/administartor user check option.
Next
From: Bruce Momjian
Date:
Subject: Re: Forcing current WAL file to be archived