Re: sql_drop Event Trigger
От | Dimitri Fontaine |
---|---|
Тема | Re: sql_drop Event Trigger |
Дата | |
Msg-id | m27gmlmwjg.fsf@2ndQuadrant.fr обсуждение исходный текст |
Ответ на | Re: sql_drop Event Trigger (Alvaro Herrera <alvherre@2ndquadrant.com>) |
Ответы |
Re: sql_drop Event Trigger
|
Список | 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 по дате отправления: