From: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Subject: Re: I propose killing PL/Tcl's "modules" infrastructure
To: Tom Lane <tgl@sss.pgh.pa.us>
References: <22067.1488046447@sss.pgh.pa.us>
 <234c68e3-47ee-4db1-fe6d-6a5de56575b6@2ndQuadrant.com>
 <23184.1488048288@sss.pgh.pa.us>
 <33fe0208-74df-1a03-08af-9a4f0d1ed14d@2ndQuadrant.com>
 <24478.1488050485@sss.pgh.pa.us>
Cc: pgsql-hackers@postgresql.org, Jan Wieck <jan@wi3ck.info>
Message-ID: <45faa542-212a-5225-2b62-c80a8df2d0fd@2ndQuadrant.com>
Date: Sat, 25 Feb 2017 15:11:12 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <24478.1488050485@sss.pgh.pa.us>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org


On 02/25/2017 02:21 PM, Tom Lane wrote:
> Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
>> On 02/25/2017 01:44 PM, Tom Lane wrote:
>>> Yeah, the only part that's even a bit hard to replicate in userland is
>>> initializing the autoloading mechanism in each session.  It would be
>>> cleaner to provide a feature similar to what you describe that could
>>> be used for that purpose as well as others.  However, where does the
>>> "parameterless function" come from?  Is it a regular PLv8 (or for this
>>> purpose PL/Tcl) function expected to be present in pg_proc?
>> Yes, it's a regular PLv8 function.
> OK ... how do you handle security considerations?  Can the GUC be set
> at any time/by anybody?  What determines whether you have permissions
> to call the particular function?
>
> 			


It can be set by anyone, IIRC. Maybe it should be SUSET only, I don't
know. It's executed as the session owner. Execute permission on the
function are determined the same way as for any function. It's an
ordinary function call. The only difference is in how the call gets
triggered.

cheers

andrew


-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers