Re: plpgsql by default

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>
Cc: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, andrew(at)supernews(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: plpgsql by default
Date: 2006-04-13 13:50:13
Message-ID: 200604131350.k3DDoDN09795@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Marc G. Fournier wrote:
> On Tue, 11 Apr 2006, Joshua D. Drake wrote:
>
> >
> >> Can you guarantee unequivocally that there are absolutely not security
> >> issues in plpgsql?
> >
> > Can you guarantee unequivocally that there are absolutely not security issues
> > in PostgreSQL?
>
> No, but does that mean we should increase the potential by adding in
> something that not everyone that runs PostgreSQL actually uses?

Now that we throw a clear suggestion to use createlang for people who
try to create plpgsql functions, the requests to include plpgsql by
default has dropped to almost zero:

test=> create function x() as '' language 'plpgsql';
ERROR: language "plpgsql" does not exist
HINT: Use CREATE LANGUAGE to load the language into the database.

--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message mark 2006-04-13 14:20:10 Re: GPUSort project
Previous Message Stephen Frost 2006-04-13 13:34:10 Re: Practical impediment to supporting multiple SSL libraries