Re: BUG #15106: The AFTER trigger is created separately on view, and the DML operation can not trigger the trigger

=?utf-8?q?PG_Bug_reporting_form?= <noreply@postgresql.org> writes:
> It can be seen from the above example, the DML operation cannot trigger the
> trigger when the Statement-level AFTER trigger is created on view alone. 
> But when create INSTEAD OF trigger at the same time, the DML operation can
> trigger the AFTER trigger.

When there's no INSTEAD OF trigger, the query is rewritten into an insert
on the view's base table (assuming the view is simple enough to be
auto-updatable), and we fire the base table's statement triggers, not the
view's.  I'm pretty sure this is intentional, though I couldn't find it
mentioned in the manual either.  Firing both sets of statement triggers
would be confusing, and not firing the base table's triggers would
perhaps miss processing that needs to happen.

			regards, tom lane