*** pgsql/doc/src/sgml/pltcl.sgml 2005/01/22 23:05:48 2.33.4.1 --- pgsql/doc/src/sgml/pltcl.sgml 2010/05/13 18:29:45 2.33.4.2 *************** *** 1,5 **** --- 1,5 ---- *************** CREATE TRIGGER trig_mytab_modcount BEFOR *** 664,671 **** It recognizes a special table, pltcl_modules, which is presumed to contain modules of Tcl code. If this table exists, the module unknown is fetched from the table ! and loaded into the Tcl interpreter immediately after creating ! the interpreter. While the unknown module could actually contain any --- 664,673 ---- It recognizes a special table, pltcl_modules, which is presumed to contain modules of Tcl code. If this table exists, the module unknown is fetched from the table ! and loaded into the Tcl interpreter immediately before the first ! execution of a PL/Tcl function in a database session. (This ! happens separately for PL/Tcl and PL/TclU, if both are used, ! because separate interpreters are used for the two languages.) While the unknown module could actually contain any *************** CREATE TRIGGER trig_mytab_modcount BEFOR *** 692,698 **** The tables pltcl_modules and pltcl_modfuncs must be readable by all, but it is wise to make them owned and ! writable only by the database administrator. --- 694,704 ---- The tables pltcl_modules and pltcl_modfuncs must be readable by all, but it is wise to make them owned and ! writable only by the database administrator. As a security ! precaution, PL/Tcl will ignore pltcl_modules (and thus, ! not attempt to load the unknown module) unless it is ! owned by a superuser. But update privileges on this table can be ! granted to other users, if you trust them sufficiently.