X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id 9ED9F53B9F
	for <pgsql-interfaces-postgresql.org@localhost.postgresql.org>;
	Thu, 21 Apr 2005 18:34:51 -0300 (ADT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 00670-07
	for <pgsql-interfaces-postgresql.org@localhost.postgresql.org>;
	Thu, 21 Apr 2005 21:32:07 +0000 (GMT)
Received: from cepheus.email.starband.net (cepheus.email.starband.net
	[148.78.247.123])
	by svr1.postgresql.org (Postfix) with ESMTP id E67F553B94
	for <pgsql-interfaces@postgresql.org>;
	Thu, 21 Apr 2005 18:07:41 -0300 (ADT)
Received: from 192.168.0.184 (vsat-148-63-169-95.c189.t7.mrt.starband.net
	[148.63.169.95]) (authenticated bits=0)
	by cepheus.email.starband.net (8.12.11/8.12.11) with ESMTP id
	j3LL5YZg019238; Thu, 21 Apr 2005 17:05:39 -0400
Subject: Re: plperl user function
From: Korry <korry@starband.net>
To: "Joshua D. Drake" <jd@commandprompt.com>
Cc: KeithW@narrowpathinc.com,
	PostgreSQL Interfaces <pgsql-interfaces@postgresql.org>
In-Reply-To: <42680F29.4030907@commandprompt.com>
References: <20050421194438.M68704@narrowpathinc.com>
	<42680480.7080805@commandprompt.com>
	<20050421200109.M30783@narrowpathinc.com>
	<42680F29.4030907@commandprompt.com>
Content-Type: multipart/alternative; boundary="=-/STdrquV7thzgP8W+l67"
Date: Thu, 21 Apr 2005 17:07:26 +0000
Message-Id: <1114103246.7513.19.camel@sakai>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.2 (2.0.2-3) 
X-Virus-Scanned: ClamAV 0.80/816/Fri Apr  8 20:46:45 2005
	clamav-milter version 0.80j on cepheus
X-Virus-Status: Clean
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.144 tagged_above=0 required=5 tests=AWL,
	FORGED_RCVD_HELO, HTML_50_60, HTML_MESSAGE
X-Spam-Level: 
X-Archive-Number: 200504/71
X-Sequence-Number: 5487


--=-/STdrquV7thzgP8W+l67
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

> > Another question:  Is there an issue with using the untrusted perl language? 
> 
> IIRC you have to be a postgresql superuser (postgres) to execute an 
> untrusted language function.


I think you meant "you have to be a postgresql superuser to create an
untrusted language function".  IIRC, a normal user can execute a
function written in an untrusted language (assuming that s/he holds the
proper EXECUTE privileges), but only a cluster superuser can create a
function written in an untrusted language.  Otherwise, it would be
difficult to create a trigger in an untrusted language. 

        -- Korry

--=-/STdrquV7thzgP8W+l67
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.3.2">
</HEAD>
<BODY>
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">&gt; Another question:  Is there an issue with using the untrusted perl language? </FONT>

<FONT COLOR="#000000">IIRC you have to be a postgresql superuser (postgres) to execute an </FONT>
<FONT COLOR="#000000">untrusted language function.</FONT>
</PRE>
</BLOCKQUOTE>
<BR>
I think you meant &quot;<FONT COLOR="#000000">you have to be a postgresql superuser to </FONT><FONT COLOR="#000000"><I><U>create</U></I></FONT><FONT COLOR="#000000"> an untrusted language function&quot;.&nbsp; </FONT>IIRC, <FONT COLOR="#000000">a normal user can </FONT><FONT COLOR="#000000"><I>execute</I></FONT><FONT COLOR="#000000"> a function written in an untrusted language (assuming that s/he holds the proper EXECUTE privileges), but only a cluster superuser can </FONT><FONT COLOR="#000000"><I>create</I></FONT><FONT COLOR="#000000"> a function written in an untrusted language.&nbsp; Otherwise, it would be difficult to create a trigger in an untrusted language. </FONT><BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Korry
</BODY>
</HTML>

--=-/STdrquV7thzgP8W+l67--