Because the trigger uses the clause, it might be executed multiple times, such as when updating or deleting multiple rows.
You might omit this clause if you just want to record the fact that the operation occurred, but not examine the data for each row.
If this privilege is later revoked, you can drop the trigger but not alter it.
The object privileges to the schema objects referenced in the trigger body must be granted to the trigger owner explicitly (not through a role).
You’ll be able to find the exact spot to turn off pain.
And more importantly - you’ll be the one calling the shots.
The statements in the trigger body operate under the privilege domain of the trigger owner, not the privilege domain of the user issuing the triggering statement (this is similar to the privilege model for stored subprograms).