| From: | "Neil Conway" <neilc(at)samurai(dot)com> |
|---|---|
| To: | "Joe Conway" <mail(at)joeconway(dot)com> |
| Cc: | "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: statement level trigger causes pltcl, |
| Date: | 2003-08-04 08:09:47 |
| Message-ID: | 3181.24.192.127.231.1059984587.squirrel@mailbox.samurai.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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 update PL/TCL -- you're welcome to go ahead and fix PL/Python
as well, if you're so inclined.
-Neil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Pflug | 2003-08-04 08:47:36 | Re: Release changes |
| Previous Message | Oleg Bartunov | 2003-08-04 06:23:36 | Re: Release changes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lee Kindness | 2003-08-04 10:25:36 | Re: 7.4 COPY BINARY Format Change |
| Previous Message | Joe Conway | 2003-08-04 05:45:06 | Re: [HACKERS] statement level trigger causes pltcl, plpython SIGSEGV |