From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
cc: pgsql-hackers@postgresql.org, Jan Wieck <jan@wi3ck.info>
Subject: Re: I propose killing PL/Tcl's "modules" infrastructure
In-reply-to: <33fe0208-74df-1a03-08af-9a4f0d1ed14d@2ndQuadrant.com>
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>
Comments: In-reply-to Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
	message dated "Sat, 25 Feb 2017 13:55:26 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <24477.1488050485.1@sss.pgh.pa.us>
Date: Sat, 25 Feb 2017 14:21:25 -0500
Message-ID: <24478.1488050485@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

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?

			regards, tom lane


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