Re: sql_drop Event Trigger - Mailing list pgsql-hackers

From Robert Haas
Subject Re: sql_drop Event Trigger
Date
Msg-id CA+TgmoYH--zrt9STdTWbwpZyYM6cKch2ZS0nGSbg9Dw-1XDVVA@mail.gmail.com
Whole thread Raw
In response to Re: sql_drop Event Trigger  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
Responses Re: sql_drop Event Trigger  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
List pgsql-hackers
On Thu, Feb 14, 2013 at 3:39 PM, Dimitri Fontaine
<dimitri@2ndquadrant.fr> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> Wait, I'm confused.  I had a note to myself to come back and review
>> this, but now that I look at it, I didn't think that patch was pending
>> review.  Alvaro, Tom, and I all made comments that seems to impinge
>> upon that design rather heavily.  No?
>
> The current design follows exactly your comments and design requests.
> Tom and Álvaro comments are the ones you did answer to saying that it's
> not 9.3 material, but next release at best, subject to heavy refactoring.
>
> What did I miss?

Well, there's this, upon which we surely have not achieved consensus:

http://www.postgresql.org/message-id/CA+TgmobQ6NGsxGuiHWqcygF0Q+7Y9zHNERePo3S1vsWKKNw2TQ@mail.gmail.com

And then Tom also wrote this, which is kind of a good point, too:

> Well, a list of object OIDs is of exactly zero use once the command
> has been carried out.  So I don't think that that represents a useful
> or even very testable feature on its own, if there's no provision to
> fire user code while the OIDs are still in the catalogs.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Kevin Grittner
Date:
Subject: Re: Materialized views WIP patch
Next
From: Robert Haas
Date:
Subject: Re: Materialized views WIP patch