
Bruce, 

My email (below) to the pgsql-ports list with my workaround patch was
bounced, but you were cc'ed also. Could you forward the appropriate info
to whomever would appreciate it most?

Thanks,
David

-- 
/==============================\
| David Mansfield              |
| david@cobite.com             |
\==============================/

---------- Forwarded message ----------

> 
> Jan, this is yours.
> 

Actually, I made a 'workaround' fix to this problem (after posting this
bug report). I'll append the patch.  I don't pretend to understand the
internals of this system, but my guess is that a simple statement like
'notify xyz' went through the planner, got an spi_plan, but the 'plan
list' was empty.  So here's my patch, which may be fixing a symptom, not
the cause, YMMV:

--- pl_exec.c~  Wed May 26 03:07:39 1999
+++ pl_exec.c   Fri Jun 25 11:00:53 1999
@@ -2482,6 +2482,10 @@
 
        plan = (Plan *) lfirst(spi_plan->ptlist);
 
+       /* it would seem as though plan can be null... --DAVID */
+       if (plan == NULL)
+               return;
+
        /* ----------
         * 2. It must be a RESULT plan --> no scan's required
         * ----------





Thu, 8 Jul 1999 13:15:36 -0400 (EDT)
David Mansfield <david@cobite.com>
RE: (bounced, help me!) [PORTS] Port Bug Report: calling notify in
	pl/pgsql proc causes core dump