From 5a67d7618f34a26b441ee5180924e57be430a220 Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Fri, 13 Aug 2004 16:17:19 +0000
Subject: [PATCH] Clarify trigger function return convention, per Thomas
 Hallgren.

---
 doc/src/sgml/trigger.sgml | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/doc/src/sgml/trigger.sgml b/doc/src/sgml/trigger.sgml
index a8ee6c7d951..56dfec80e6c 100644
--- a/doc/src/sgml/trigger.sgml
+++ b/doc/src/sgml/trigger.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/trigger.sgml,v 1.35 2004/03/03 22:22:24 neilc Exp $
+$PostgreSQL: pgsql/doc/src/sgml/trigger.sgml,v 1.36 2004/08/13 16:17:19 tgl Exp $
 -->
 
  <chapter id="triggers">
@@ -431,8 +431,10 @@ typedef struct Trigger
    </para>
 
    <para>
-    A trigger function must return either <symbol>NULL</> or a
-    <structname>HeapTuple</> pointer.  Be careful to return either
+    A trigger function must return either a
+    <structname>HeapTuple</> pointer or a <symbol>NULL</> pointer
+    (<emphasis>not</> a SQL NULL, that is, do not set isNull true).
+    Be careful to return either
     <structfield>tg_trigtuple</> or <structfield>tg_newtuple</>,
     as appropriate, if you don't want to modify the row being operated on.
    </para>