fastpath neglected to pass a valid isNull flag to the function being

called.  We hadn't noticed this because C-coded functions mostly don't
pay attention to isNull anyway ... but plpgsql functions sure do ...
This is fixed in another way for 7.1, but 7.0.1 needs this patch.

diff --git a/src/backend/tcop/fastpath.c b/src/backend/tcop/fastpath.c
index 1b38fe7ed08e4098bf99e10abf944c6461f7cc64..c6ac986cbbf91ce7f73a956a07aeef3f9426c6a9 100644 (file)
--- a/src/backend/tcop/fastpath.c
+++ b/src/backend/tcop/fastpath.c
@@ -8,7 +8,7 @@
  *
  *
  * IDENTIFICATION
- *   $Header: /cvsroot/pgsql/src/backend/tcop/fastpath.c,v 1.38 2000/04/12 17:15:43 momjian Exp $
+ *   $Header: /cvsroot/pgsql/src/backend/tcop/fastpath.c,v 1.38.2.1 2000/05/28 15:40:25 tgl Exp $
  *
  * NOTES
  *   This cruft is the server side of PQfn.
@@ -363,6 +363,7 @@ HandleFunctionRequest()
    }
 
 #ifndef NO_FASTPATH
+   isNull = false;
    retval = fmgr_array_args(fid, nargs, arg, &isNull);
 #else
    retval = NULL;