From: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Friedrich Dodt <friedrich(dot)dodt(at)efonds24(dot)de>, pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: Where is PLbash ?? |
Date: | 2002-06-26 07:49:39 |
Message-ID: | 20020626094938.A19070@zf.jcu.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
On Tue, Jun 25, 2002 at 01:52:41PM -0400, Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Peter, can we add PL/sh into CVS for 7.3?
>
> I'm kind of against adding PL/sh to CVS, ever; and I believe Peter is
> too, else he'd have done it already.
>
> I know you will say that PL/sh is not any more dangerous than the
> untrusted versions of plperl and pltcl, but there is a difference.
> PL/sh has *no reason to exist* other than to implement
> non-transaction-safe outside-the-database behavior; there is no safe
> behavior for which it is the preferred tool. I think making it easily
> available is a bad idea, because people *will* shoot themselves in the
> foot with it.
:-) In my Debian is available a lot of non-safe programs and utils...
I think people have own brain and if documentation warn about PL/sh
it's enough. (BTW, default Apache distribution contains shell based
CGI script and people can write others own shell scripts -- it's
interesting, but people more use PHP/Perl/Python/etc. Why? Because
they good know what is better/safe.)
Karel
--
Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>
http://home.zf.jcu.cz/~zakkr/
C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
From | Date | Subject | |
---|---|---|---|
Next Message | Nick Haw | 2002-06-26 09:29:37 | Views, Access 2000 and write conflicts |
Previous Message | Bruce Momjian | 2002-06-26 03:12:33 | Re: Where is PLbash ?? |