Re: sql_drop Event Trigger - Mailing list pgsql-hackers

From Dimitri Fontaine
Subject Re: sql_drop Event Trigger
Date
Msg-id m27gmlmwjg.fsf@2ndQuadrant.fr
Whole thread Raw
In response to Re: sql_drop Event Trigger  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: sql_drop Event Trigger
List pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.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



pgsql-hackers by date:

Previous
From: Miroslav Šimulčík
Date:
Subject: Re: function for setting/getting same timestamp during whole transaction
Next
From: Pavel Stehule
Date:
Subject: Re: function for setting/getting same timestamp during whole transaction