Re: sql_drop Event Trigger
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Dimitri Fontaine <dimitri@2ndquadrant.fr>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2013-02-16T01:20:10Z
Lists: 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