Re: sql_drop Event Triggerg

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: sql_drop Event Triggerg
Date: 2013-03-08 13:28:27
Message-ID: CA+TgmobtGyfMuJRdW3pDND3sp=+Saa7Jf5cWT93BC8ig3LTrsw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 5, 2013 at 12:45 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2013-03-08 13:32:06 Re: Index Unqiueness
Previous Message Heikki Linnakangas 2013-03-08 13:08:02 Re: SP-GiST for ranges based on 2d-mapping and quad-tree