aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/xfunc.sgml15
1 files changed, 0 insertions, 15 deletions
diff --git a/doc/src/sgml/xfunc.sgml b/doc/src/sgml/xfunc.sgml
index 35d34f224ef..8074f66417d 100644
--- a/doc/src/sgml/xfunc.sgml
+++ b/doc/src/sgml/xfunc.sgml
@@ -234,21 +234,6 @@ CALL clean_emp();
whereas returning <type>void</type> is a PostgreSQL extension.
</para>
- <note>
- <para>
- The entire body of an SQL function is parsed before any of it is
- executed. While an SQL function can contain commands that alter
- the system catalogs (e.g., <command>CREATE TABLE</command>), the effects
- of such commands will not be visible during parse analysis of
- later commands in the function. Thus, for example,
- <literal>CREATE TABLE foo (...); INSERT INTO foo VALUES(...);</literal>
- will not work as desired if packaged up into a single SQL function,
- since <structname>foo</structname> won't exist yet when the <command>INSERT</command>
- command is parsed. It's recommended to use <application>PL/pgSQL</application>
- instead of an SQL function in this type of situation.
- </para>
- </note>
-
<para>
The syntax of the <command>CREATE FUNCTION</command> command requires
the function body to be written as a string constant. It is usually