Re: pl/Ruby, deprecating plPython and Core

From: Tino Wildenhain <tino(at)wildenhain(dot)de>
To: josh(at)agliodbs(dot)com
Cc: pgsql-hackers(at)postgresql(dot)org, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, David Fetter <david(at)fetter(dot)org>
Subject: Re: pl/Ruby, deprecating plPython and Core
Date: 2005-08-17 06:16:47
Message-ID: 4302D64F.303@wildenhain.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Josh Berkus schrieb:
> People:
>
> How about we draft some criteria for inclusion of a PL in the main distro?
>
> Suggestions:
>
> 1) The PL must be "stable" (that is, not capable of crashing the backend)
> 2) The PL must be buildable only using --with-{lang} and createlang
> (assuming that the user has the correct libraries)
> 3) There must be a regression test included, which tests both creating the
> lang and creating+executing a small function in it.
> 4) The PL must have at least one maintainer who subscribes to
> pgsql-hackers.
> 5) It must be possible to build the PL without changing the licensing of
> PostgreSQL (this excludes PL/R, unfortunately).
>
> Controversial Criterion:
> 6) The PL should be buildable in "trusted" mode. (I vote no on this one)
>
> I, myself, do not think that either popularity or inclusion of the language
> in Linux distros should be a criterion. If PL/Haskell or PL/Smalltalk
> catches on with *our* community it should be good enough for us. Heck,
> were it not for the licensing and build issues, I'd be advocating strongly
> fro PL/R.

+1 on all of this from me

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2005-08-17 07:48:38 Re: Missing CONCURRENT VACUUM (Was: Release notes for
Previous Message Tom Lane 2005-08-17 03:53:04 Re: Race conditions, race conditions!