Robert Haas <robertmh...@gmail.com> writes: >> 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. > > Well, that could result in some DROP events being reported more than > once, which I assume would be undesirable for someone hoping to use > this for replication.
Any command might have an event trigger attached doing a DROP, so that you don't know where to expect it, and it's well possible that in your example both the event triggers have been installed by different tools. -- 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
