From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Steven Bradley <sbradley(at)llnl(dot)gov> |
Cc: | pgsql-interfaces(at)hub(dot)org |
Subject: | Re: triggers and NOTIFY |
Date: | 1999-07-04 01:20:45 |
Message-ID: | 17308.931051245@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
Steven Bradley <sbradley(at)llnl(dot)gov> writes:
> When the trigger simply
> issues the NOTIFY, the front-end process recieves the notification just
> fine. However, when I also try to INSERT a record into table B from within
> the trigger (either before or after issuing the NOTIFY), the record gets
> inserted into table B, but the front-end application does not recieve a
> notification.
What version are you using? The test case you gave causes a repeatable
core dump in 6.5 for me, so it was pretty easy to find the cause.
I have committed a fix for 6.5.1, but if you are in a hurry:
*** pl/plpgsql/src/pl_exec.c.orig Tue May 25 12:15:17 1999
--- pl/plpgsql/src/pl_exec.c Sat Jul 3 21:03:01 1999
***************
*** 2486,2491 ****
--- 2486,2494 ----
* 2. It must be a RESULT plan --> no scan's required
* ----------
*/
+ if (plan == NULL) /* utility statement produces this */
+ return;
+
if (nodeTag(plan) != T_Result)
return;
This might be the same problem that someone (Vince, maybe?) was
complaining about a couple months ago --- I didn't look into it
at the time.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Herouth Maoz | 1999-07-04 10:10:17 | Re: [INTERFACES] Time and microseconds? |
Previous Message | Anton de Wet | 1999-07-03 13:48:54 | using libpgtcl with netscape tcl plugin? |