Re: [HACKERS] statement level trigger causes pltcl, plpython SIGSEGV

2003-08-14 Thread Joe Conway
elein wrote: I thought that statement level triggers did not work yet. Are they supposed to work in 7.4? (But even if they don't work they shouldn't crash...) Yeah, they work - not as everyone would like, but they work. All fixed now anyway. Joe ---(end of broadcast)--

Re: [HACKERS] statement level trigger causes pltcl, plpython SIGSEGV

2003-08-14 Thread elein
I thought that statement level triggers did not work yet. Are they supposed to work in 7.4? (But even if they don't work they shouldn't crash...) elein On Sun, Aug 03, 2003 at 08:04:11PM -0700, Joe Conway wrote: > I was working on trigger support for PL/R and ran across this bug in my > own cod

Re: [HACKERS] statement level trigger causes pltcl,

2003-08-04 Thread Neil Conway
Joe Conway said: > Hmm, same problem. Looks like PL/pgSQL does the right thing, but > plpython will crash also. I don't think plperl supports triggers. Right -- I only had time to implement support for statement-level triggers in the backend itself and in PL/PgSQL. Thanks for taking the time to up

[HACKERS] statement level trigger causes pltcl, plpython SIGSEGV

2003-08-03 Thread Joe Conway
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=