*** pgsql/doc/src/sgml/plperl.sgml 2003/08/31 17:32:19 2.20 --- pgsql/doc/src/sgml/plperl.sgml 2010/05/13 16:44:35 2.20.2.1 *************** *** 1,5 **** --- 1,5 ---- *************** CREATE FUNCTION badfunc() RETURNS intege *** 259,265 **** If the above function was created by a superuser using the language plperlu, execution would succeed. ! Missing Features --- 259,284 ---- If the above function was created by a superuser using the language plperlu, execution would succeed. ! ! ! ! For security reasons, to stop a leak of privileged operations from ! PL/PerlU to PL/Perl, these two languages ! have to run in separate instances of the Perl interpreter. If your ! Perl installation has been appropriately compiled, this is not a problem. ! However, not all installations are compiled with the requisite flags. ! If PostgreSQL detects that this is the case then it will ! not start a second interpreter, but instead create an error. In ! consequence, in such an installation, you cannot use both ! PL/PerlU and PL/Perl in the same backend ! process. The remedy for this is to obtain a Perl installation created ! with the appropriate flags, namely either usemultiplicity or ! both usethreads and useithreads. ! For more details,see the perlembed manual page. ! ! ! ! Missing Features