|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/plperl.sgml,v 2.69 2008/04/10 15:16:46 alvherre Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/plperl.sgml,v 2.70 2009/08/15 00:33:12 petere Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="plperl"> |
4 | 4 | <title>PL/Perl - Perl Procedural Language</title> |
@@ -72,8 +72,10 @@ $$ LANGUAGE plperl; |
72 | 72 | they refer to lexical variables in the enclosing scope. Because a PL/Perl |
73 | 73 | function is wrapped in a subroutine, any named subroutine you create will |
74 | 74 | be nested. In general, it is far safer to create anonymous subroutines |
75 | | - which you call via a coderef. See the <literal>perldiag</literal> |
76 | | - man page for more details. |
| 75 | + which you call via a coderef. See <literal>Variable "%s" will not stay shared</literal> |
| 76 | + and <literal>Variable "%s" is not available</literal> in the |
| 77 | + <citerefentry><refentrytitle>perldiag</></citerefentry> man page for more |
| 78 | + details. |
77 | 79 | </para> |
78 | 80 | </note> |
79 | 81 |
|
|