Dimitri Fontaine escribió: > Robert Haas <robertmh...@gmail.com> writes:
> > I have not tested the actual behavior of the latest patch, but I think > > we want to define things so that the > > pg_event_trigger_dropped_objects() function returns, specifically, the > > list of objects dropped by the command which caused the event trigger > > to fire. In other words, in the above example, the first, recursive > > invocation of B should see the object removed by A's DROP-IF-EXISTS, > > and the second invocation should see the object removed by the > > toplevel command. > > I disagree with that. I don't see why the enclosing event trigger > shouldn't be aware of all the objects dropped by the command that just > ran to completion, *including* the effects of any event trigger fired > recursively or not. Not sure about that. If the trigger records objects dropped in a table, aren't they going to show up there twice if you do that? -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
