| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: [COMMITTERS] pgsql: Add sql_drop event for event triggers |
| Date: | 2013-04-09 15:51:05 |
| Message-ID: | 2347.1365522665@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> (Someone might still complain that we cause a PG_TRY in BEGIN
> TRANSACTION etc. Not sure if this is something we should worry about.
> Robert did complain about this previously.)
I think it would be difficult and probably dangerous to have PG_TRY
for only some utility commands, so not much to be done about that.
The main thing is to not invoke event trigger code for BEGIN/ABORT/SET.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2013-04-09 15:56:01 | Re: [COMMITTERS] pgsql: Add sql_drop event for event triggers |
| Previous Message | Alvaro Herrera | 2013-04-09 15:44:02 | Re: [COMMITTERS] pgsql: Add sql_drop event for event triggers |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2013-04-09 15:56:01 | Re: [COMMITTERS] pgsql: Add sql_drop event for event triggers |
| Previous Message | Alvaro Herrera | 2013-04-09 15:44:02 | Re: [COMMITTERS] pgsql: Add sql_drop event for event triggers |