From d98039d8966dee1ce8a7dfc8687ebdbb4d77b3c6 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Thu, 25 Feb 2010 22:24:00 +0000
Subject: [PATCH] Document that after triggers that need to see changed rows
 should not be marked stable.

---
 doc/src/sgml/ref/create_function.sgml | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/ref/create_function.sgml b/doc/src/sgml/ref/create_function.sgml
index ed5d7c5bda..3d7eadcaf8 100644
--- a/doc/src/sgml/ref/create_function.sgml
+++ b/doc/src/sgml/ref/create_function.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_function.sgml,v 1.90 2010/02/14 01:01:35 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/create_function.sgml,v 1.91 2010/02/25 22:24:00 momjian Exp $
 -->
 
 <refentry id="SQL-CREATEFUNCTION">
@@ -289,7 +289,9 @@ CREATE [ OR REPLACE ] FUNCTION
        return the same result for the same argument values, but that its
        result could change across SQL statements.  This is the appropriate
        selection for functions whose results depend on database lookups,
-       parameter variables (such as the current time zone), etc.  Also note
+       parameter variables (such as the current time zone), etc.  (It is
+       inappropriate for <literal>AFTER</> triggers that wish to
+       query rows modified by the current command.)  Also note
        that the <function>current_timestamp</> family of functions qualify
        as stable, since their values do not change within a transaction.
       </para>
-- 
2.40.0