Re: sql_drop Event Triggerg
От | Robert Haas |
---|---|
Тема | Re: sql_drop Event Triggerg |
Дата | |
Msg-id | CA+TgmobtGyfMuJRdW3pDND3sp=+Saa7Jf5cWT93BC8ig3LTrsw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: sql_drop Event Triggerg (Alvaro Herrera <alvherre@2ndquadrant.com>) |
Ответы |
Re: sql_drop Event Triggerg
|
Список | pgsql-hackers |
On Tue, Mar 5, 2013 at 12:45 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote: > Hmm, maybe I should be considering a pair of macros instead -- > UTILITY_START_DROP and UTILITY_END_DROP. I'll give this a try. Other > ideas are welcome. That seems like a possibly promising idea. I do wonder how well any of this is going to scale. Presumably people are going to want similar things for CREATE and (hardest) ALTER. Seems like ProcessUtility() could get pretty messy and confusing. But I don't have a better idea, either. :-( -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: