Re: pl/Ruby, deprecating plPython and Core

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Cc: "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-16 23:06:10
Message-ID: 200508161606.11105.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
--Josh

Josh Berkus
Aglio Database Solutions
San Francisco

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Wong 2005-08-16 23:07:30 Re: data on devel code perf dip
Previous Message Mary Edie Meredith 2005-08-16 23:02:19 Re: data on devel code perf dip