| From: | Joe Conway <mail(at)joeconway(dot)com> | 
|---|---|
| To: | "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org> | 
| Subject: | statement level trigger causes pltcl, plpython SIGSEGV | 
| Date: | 2003-08-04 03:04:11 | 
| Message-ID: | 3F2DCD2B.8080004@joeconway.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches | 
I was working on trigger support for PL/R and ran across this bug in my 
own code related to STATEMENT level triggers. I decided to try it in PL/Tcl:
regression=# CREATE FUNCTION tcltrigfunc() RETURNS trigger AS '
regression'#    return OK
regression'# ' LANGUAGE pltcl;
CREATE FUNCTION
regression=#
regression=# CREATE TRIGGER tcltrig BEFORE INSERT OR UPDATE OR DELETE ON foo
regression-#     FOR EACH STATEMENT EXECUTE PROCEDURE tcltrigfunc();
CREATE TRIGGER
regression=# insert into foo values(11,'cat99',1.89);
The connection to the server was lost. Attempting reset: Failed.
connection pointer is NULL
!>
Hmm, same problem. Looks like PL/pgSQL does the right thing, but 
plpython will crash also. I don't think plperl supports triggers.
I'll try to submit a patch later tonight or tomorrow morning if no one 
beats me to it.
Joe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Larry Rosenman | 2003-08-04 03:07:10 | Re: Release changes | 
| Previous Message | snpe | 2003-08-04 02:56:24 | Re: Release changes | 
| From | Date | Subject | |
|---|---|---|---|
| Next Message | elein | 2003-08-04 04:59:38 | Re: statement level trigger causes pltcl, plpython SIGSEGV | 
| Previous Message | Troels Arvin | 2003-08-03 20:06:35 | Re: AUTO_INCREMENT patch |