From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: sql_drop Event Trigger |
Date: | 2013-02-06 12:55:31 |
Message-ID: | m27gmlmwjg.fsf@2ndQuadrant.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Well, I don't necessarily suggest that. But how about something like
> this in performMultipleDeletions:
[edited snippet of code]
> /* invoke sql_drop triggers */
> EventTriggerSQLDrop();
>
> /* EventTriggerSQLDropList remains set for ddl_command_end triggers */
> }
>
> /* and delete them */
> for (i = 0; i < targetObjects->numrefs; i++)
...
> deleteOneObject(thisobj, &depRel, flags);
My understanding of Tom and Robert comments is that it is very unsafe to
run random user code at this point, so that can not be an Event Trigger
call point.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2013-02-06 12:58:58 | Re: function for setting/getting same timestamp during whole transaction |
Previous Message | Miroslav Šimulčík | 2013-02-06 12:26:40 | Re: function for setting/getting same timestamp during whole transaction |