On Mon, 10 Apr 2006, Joshua D. Drake wrote:
> Tom Lane wrote:
>> Andrew - Supernews <andrew+nonews@supernews.com> writes:
>>> On 2006-04-10, Bruce Momjian <pgman@candle.pha.pa.us> wrote:
>>>>> [ security ]
>>>> It actually is the reason I have heard.
>>
>>> And it was duly debunked.
>>
>> That is the reasoning, and personally I agree with it. You don't leave
>> sharp objects sitting around if you have no need to have them out.
>
> Uhmmm exactly how is plpgsql a sharp object? plPerl... ok that makes sense
> but you can't access the underlying OS with plpgsql.
Can you guarantee unequivocally that there are absolutely not security
issues in plpgsql?
I believe Tom's point is that it is not possible to do so, and, since
plpgsql isn't something that all applications need/use, it isn't something
that needs to be 'loaded by default' ... its like loading mod_perl in
apache for an application that only uses PHP ... you can do it, but why
bother?
If Tom could cite any security issues with plpgsql, he would have probably
fixed it by now ... but I don't believe he'd go out on a limb and state
that there weren't any either ...
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664