Tom Lane <t...@sss.pgh.pa.us> writes: > I have to completely disagree with that. If we don't want PostgreSQL > to soon subside into an unfixable morass, as I think Brooks puts it, > we must *not* simply patch things in a way that expediently provides > an approximation of some desired feature. We have to consider, and put > substantial weight on, having a clean and maintainable system design.
When in Ottawa next may, I will have to buy you a glass of your favorite wine and explain to you my main use case and vision. You will then realize that all this time that I've been spending on Event Triggers is a sideway to build something else entirely, because I know that it's the only way to get the feature I want in core PostgreSQL. So yes, I know about the clean and maintainable system design constraint. I've a lot to learn still, and I appreciate your help very much. Rest assured that the path you describe is the one I'm taking. > I think that we're not realistically going to be able to introduce > event triggers in very many of the places we'd like to have them > without first doing a lot of fundamental refactoring. We're only talking about ddl_command_start and ddl_command_end now. The table_rewrite event is still on the horizon, but is not realistic to get in 9.3 anymore, I think :( So we're talking about adding some call points only in utility.c, only before or after a ddl command is run, including nested sub-commands. > So my opinion is that most of what we'd like to have here is material > for 9.4 or 9.5 or even further out. If we can get the event trigger > catalog infrastructure and some *very* basic events, like > end-of-toplevel-command, into place for 9.3, we'll have done well. My feeling is that I'm sending patches that only implement the *very* basic events here, and nothing more. Most of the heat of this thread came from a discussion about a feature that's very hard to design and that is not in my patch series to review. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
