1
0
mirror of https://github.com/postgres/postgres.git synced 2025-07-23 03:21:12 +03:00

Add warning about plperl nested named subroutines

Andrew Dunstan
This commit is contained in:
Bruce Momjian
2005-10-12 14:28:33 +00:00
parent 0a28eb4622
commit 6b97e437ca

View File

@ -1,5 +1,5 @@
<!-- <!--
$PostgreSQL: pgsql/doc/src/sgml/plperl.sgml,v 2.45 2005/08/24 19:16:49 tgl Exp $ $PostgreSQL: pgsql/doc/src/sgml/plperl.sgml,v 2.46 2005/10/12 14:28:33 momjian Exp $
--> -->
<chapter id="plperl"> <chapter id="plperl">
@ -53,12 +53,24 @@ CREATE FUNCTION <replaceable>funcname</replaceable> (<replaceable>argument-types
# PL/Perl function body # PL/Perl function body
$$ LANGUAGE plperl; $$ LANGUAGE plperl;
</programlisting> </programlisting>
The body of the function is ordinary Perl code. A PL/Perl function must The body of the function is ordinary Perl code. In fact, the PL/Perl
glue code wraps it inside a Perl subroutine. A PL/Perl function must
always return a scalar value. You can return more complex structures always return a scalar value. You can return more complex structures
(arrays, records, and sets) by returning a reference, as discussed below. (arrays, records, and sets) by returning a reference, as discussed below.
Never return a list. Never return a list.
</para> </para>
<note>
<para>
The use of named nested subroutines is dangerous in Perl, especially if
they refer to lexical variables in the enclosing scope. Because a PL/Perl
function is wrapped in a subroutine, any named subroutine you create will
be nested. In general, it is far safer to create anonymous subroutines
which you call via a coderef. See the <literal>perldiag</literal>
man page for more details.
</para>
</note>
<para> <para>
The syntax of the <command>CREATE FUNCTION</command> command requires The syntax of the <command>CREATE FUNCTION</command> command requires
the function body to be written as a string constant. It is usually the function body to be written as a string constant. It is usually