Re: sql_drop Event Triggerg - Mailing list pgsql-hackers

From Robert Haas
Subject Re: sql_drop Event Triggerg
Date
Msg-id CA+TgmobtGyfMuJRdW3pDND3sp=+Saa7Jf5cWT93BC8ig3LTrsw@mail.gmail.com
Whole thread Raw
In response to Re: sql_drop Event Triggerg  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: sql_drop Event Triggerg  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List 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 by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: SP-GiST for ranges based on 2d-mapping and quad-tree
Next
From: Robert Haas
Date:
Subject: Re: Index Unqiueness