From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org, Jan Wieck <jan(at)wi3ck(dot)info> |
Subject: | Re: I propose killing PL/Tcl's "modules" infrastructure |
Date: | 2017-02-25 19:21:25 |
Message-ID: | 24478.1488050485@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2017-02-25 19:43:51 | Re: Proposal for changes to recovery.conf API |
Previous Message | David G. Johnston | 2017-02-25 19:01:42 | Re: UPDATE of partition key |