Re: I propose killing PL/Tcl's "modules" infrastructure
Tom Lane <tgl@sss.pgh.pa.us>
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>
Date: 2017-02-25T19:21:25Z
Lists: pgsql-hackers
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
Commits
-
Invent start_proc parameters for PL/Tcl.
- 0d2b1f305dc7 10.0 landed
-
Remove PL/Tcl's "module" facility.
- 817f2a586342 10.0 landed
-
Remove all of the libpgtcl and pgtclsh files, including all references to
- 41fa9e9bae60 8.0.0 cited