Commit 0dd3afad authored by Tom Lane's avatar Tom Lane

Reiterate that parsing of plpgsql functions is per-process.

parent 93f54561
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/plsql.sgml,v 2.50 2001/11/21 05:53:41 thomas Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/Attic/plsql.sgml,v 2.51 2001/11/28 04:18:46 tgl Exp $
--> -->
<chapter id="plpgsql"> <chapter id="plpgsql">
...@@ -62,7 +62,8 @@ $Header: /cvsroot/pgsql/doc/src/sgml/Attic/plsql.sgml,v 2.50 2001/11/21 05:53:41 ...@@ -62,7 +62,8 @@ $Header: /cvsroot/pgsql/doc/src/sgml/Attic/plsql.sgml,v 2.50 2001/11/21 05:53:41
<para> <para>
The <application>PL/pgSQL</> call handler parses the function's source text and The <application>PL/pgSQL</> call handler parses the function's source text and
produces an internal binary instruction tree the first time the produces an internal binary instruction tree the first time the
function is called. The instruction tree fully translates the function is called (within any one backend process). The instruction tree
fully translates the
<application>PL/pgSQL</> statement structure, but individual <application>PL/pgSQL</> statement structure, but individual
<acronym>SQL</acronym> expressions and <acronym>SQL</acronym> queries <acronym>SQL</acronym> expressions and <acronym>SQL</acronym> queries
used in the function are not translated immediately. used in the function are not translated immediately.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment